Offset paging skipped rows when records were inserted mid-scan; cursors fixed it.
Conversation
Turn 1 — User
Clients paging through the list endpoint are missing records.
Turn 2 — Assistant
Classic offset problem — a row inserted before the current offset shifts everything and the next page skips one. I moved to cursor paging keyed on a stable sort column plus the primary key as a tiebreak.
The cursor is opaque to clients and encodes both values, so ordering stays stable even when rows are inserted mid-scan.
Turn 3 — User
Is the old parameter still accepted?
Turn 4 — Assistant
Yes, for now — it still works and returns a deprecation header. Removing it is a breaking change and belongs in a version bump.
Subjects
- [[REST API]]
- [[SQLite]]
- [[Python]]