Pagination by page numbers

[aprilmintacpineda]

Currently, the way pagination work is by providing after which corresponds to the ref.id, this is pagination by nextToken, what about pagination by page numbers?

like: ?page=100

say there are 500 pages in total and you want to go to page 189, do we make the user go through pages 1 to 188 to before reaching 189? I think that’s not a good UX.

[ptpaterson]

Hi @aprilmintacpineda!

Have you seen these existing topics?

Recommended way of doing a page offset?

This is easily translatable into fauna (assuming $LIMIT < 100k): Drop(Paginate(....., {size: $LIMIT}), $OFFSET). “But, Ben!” I hear you exclaim: “isn’t that really inefficient?”. Yes it is, and so is the SQL. What you probably want to do is keyset pagination, which is efficient, and also representable in fauna using the Range function, or using the before and after cursors.

What is the best practice for offset pagination using FaunaDB?

Hey, welcome to the forum and thanks for placing the question here. I don’t think there is a tutorial that already handles counts, hence why I asked you to place this question here. If there are any, our community will surely respond over time! In the meantime, I’ll write down some extra info and recommendations. Pagination in FaunaDB indeed does not provide any count information by default but it’s fairly easy to get that count yourself. It would be quite hard for FaunaDB to get you that coun…

[ptpaterson]

To specifically address UX for getting to page 189, I think the best UX would be a filter/search that reduce results (and pages), or otherwise skipping undesired data. It’s not good UX either if the user has to rely on knowing that the data they want is on page 189/500.

[aprilmintacpineda]

It’s odd that when I searched for pagination those didn’t appear… thanks for the kind response!