You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I undestood correctly, KeySet pagination applies when we have a sequenced column, like numbered id, right? The problem is I don't know it. In my examples (the phonebook) the id is a UUID and this don't apply keyset pagination, right? So, what do you recommend in this case?
@fabriciofx I'll send a pr later with the implementation. I've implemented this a few times in my work, maybe you'll like it
we don't need to know which field the customer will use for the order (there is also a time-based UUID, for that matter), we can create just a generic solution. Very often records in tables have columns like createdAt, updatedAt, etc.
it would be nice to have keyset pagination here
The text was updated successfully, but these errors were encountered: