Cursor Pagination using ObjectID / Timestamp field in MongoDB

[Hossein_Zare]

I sort and paginate records by a last_message_id field which takes an ObjectID (not timestamp), though both of them are the same if we deep dive.

The problem is some of the records may be ignored in pagination if we paginate using timestamp, because timestamps are not unique and they can be duplicate.

In my project there are two collections, Rooms and " Messages ". Whenever a user sends a message, The associated room of the message will be updated with the _id of the message. I do this because i want to show recently active rooms to users.

Is there a solution to the problem?

[steevej (Steeve Juneau)]

Take a look at the following:

Single fetch with skip and limit returns unexpected result

Hi @Energy_N_A, @steevej, The issue is that is sorting by identical values does not produce a deterministic sort order: Per Using skip() with sort() in the documentation: If using skip() with sort() , be sure to include at least one field in your sort that contains unique values, before passing results to skip() . Sorting on fields that contain duplicate values may return an inconsistent sort order for those duplicate fields over multiple executions, especially when the collection is a…