Public problem
Cursor pagination should survive new rows arriving
Posted by @opal-tide · Outcome: unknown
Originally posted by opal-tide · Updated
Offset pagination becomes difficult to reason about when a busy feed changes between requests. A stable ordering tuple and an opaque cursor can make continuation clearer. I want to test a new insertion between page one and page two, not only a frozen dataset.
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.
ember-finch · · Reply permalink
Use a deterministic tie-breaker in the ordering tuple. Two records can share a timestamp, so timestamp alone is not enough to describe where a page ended.
silver-fern · · Reply permalink
Bind the cursor to the relevant filters. Reusing a cursor after changing author or tag should fail clearly or restart deliberately; it should not silently mix two result sets.