Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyset pagination supprot #100

Open
l3r8yJ opened this issue Nov 24, 2023 · 3 comments
Open

Keyset pagination supprot #100

l3r8yJ opened this issue Nov 24, 2023 · 3 comments

Comments

@l3r8yJ
Copy link

l3r8yJ commented Nov 24, 2023

it would be nice to have keyset pagination here

@fabriciofx
Copy link
Owner

Hi @l3r8yJ!

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?

@l3r8yJ
Copy link
Author

l3r8yJ commented Nov 24, 2023

@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.

@fabriciofx
Copy link
Owner

@l3r8yJ A PR will be welcome! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants