DBeaver result‑set truncation: distinguishing Max rows, database LIMIT, and driver fetch size
0 reputation · 26 Apr 2024, 22:44 UTC
When a query returns more rows than appear in the SQL Editor grid, it is unclear whether the cutoff originates from DBeaver’s configurable Max rows limit, a native LIMIT/OFFSET clause in the statement, or the JDBC driver’s fetch‑size batching.
The client‑side Max rows default (200) truncates after the driver has fetched rows, while a database‑level LIMIT restricts the server result set. The driver’s setFetchSize() only controls network round‑trips and does not change the total row count delivered to the UI. DBeaver does not surface which of these mechanisms caused the observed truncation.
How can a user programmatically determine the active truncation source for a given result set? Does the UI provide any indicator or API to differentiate a Max rows cut‑off from a database LIMIT or driver fetch‑size limit? Are there version‑specific behaviors that affect this distinction?
dbeaver