Open Stack

> @Michael - I suggest just using a simple stable batch marker - e.g.
> the unique key of the edge of the batch - which is stable enough to
> handle inserts and deletes without double-showing or skipping rows.

It can handle inserts and deletes, but it's not stable if you order by a column such as status, or updated time, or, assignee... because those values might change as you browse, and so records would jump around pages. And if the record you're using as a marker changes position in the list, you could be thrown way forward or backward without knowing it.

Mike