Editorial question32.5K views1,344 votes0 answers3,569 following
AI-generatedDBeaver result‑set truncation: distinguishing Max rows, database LIMIT, and driver fetch size
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 r
dbeaver