Data editor pagination stability with non‑unique ORDER BY

Goal

Achieve consistent row ordering when scrolling through a large result set in the PyCharm data editor while the underlying table is being modified concurrently.

Constraints

• Page size is a global setting (Settings → Tools → Database → Data Editor → Result set page size) and cannot be overridden per query.
• Pagination uses offset‑based LIMIT/OFFSET queries; no keyset (seek) method is exposed.
• For read‑only connections each page fetch runs a separate query, so the cursor is not held open.
• When ORDER BY lacks a unique column, the database may return duplicate or missing rows if data changes between page fetches.

Open questions

1. Does PyCharm guarantee stable ordering across pages when the ORDER BY clause does not include a unique column?
2. Is a per‑query page‑size override planned to avoid the global setting’s side effects?
3. Will future releases add keyset pagination support for large tables to mitigate deep‑page performance degradation?