DataSpell Database Console Pagination with Large OFFSET

DataSpell Database Console Pagination with Large OFFSET

Goal

Determine how DataSpell’s Database Console handles pagination when the OFFSET value is very large, and whether the tool can be configured to enforce server‑side pagination to avoid excessive client memory usage.

Constraints

DataSpell automatically appends LIMIT/OFFSET clauses via its UI pagination controls, but the underlying JDBC driver may retrieve the full result set before applying the offset. This behavior varies across database types and may change with future releases. No documented setting currently exists to force server‑side pagination or streaming of results.

Unresolved Questions

• Does DataSpell’s Database Console always transmit the entire result set for large OFFSET values, or does it rely on the database engine to apply the offset server‑side?
• Can a configuration or flag be introduced to force server‑side pagination or streaming for large result sets?
• How does the behavior differ between popular JDBC drivers (e.g., PostgreSQL, MySQL) when confronted with large OFFSET values in DataSpell?