Could we define a deterministic tie-breaker for each sortable resource type?
The addition of sortField is helpful, but fields like createdDate, releaseDate, version, and name are not guaranteed to be unique. Without a stable tie-breaker, cursor pagination can still produce duplicate or missing results when multiple records share the same sort value.
A simple rule could be:
Results MUST be ordered by the selected sortField, then by UUID as a deterministic tie-breaker.
This would make token pagination more reliable and easier to implement consistently.
Originally posted by @Mehrn0ush in #231 (comment)
Could we define a deterministic tie-breaker for each sortable resource type?
The addition of
sortFieldis helpful, but fields likecreatedDate,releaseDate,version, andnameare not guaranteed to be unique. Without a stable tie-breaker, cursor pagination can still produce duplicate or missing results when multiple records share the same sort value.A simple rule could be:
Results MUST be ordered by the selected sortField, then by UUID as a deterministic tie-breaker.This would make token pagination more reliable and easier to implement consistently.
Originally posted by @Mehrn0ush in #231 (comment)