#community-help

Querying Pagination & Server-side Caching

TLDR Ivy asks about pagination stability, and Jason confirms it depends on data consistency. Ivy considers using server-side caching.

5mo

Join the chat

Apr 11, 2023 (5 months ago)

Photo of md5-2f39998c05c5409f8c3521187ec34d4e

Ivy

06:52 PM

Hi all! Beautiful docs first off, some of the best I've ever read 😁 Just a quick question regarding pagination: is each page a separate query that could return different or the same results depending on if data has been modified?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

07:10 PM

Thanks Ivy!

07:10

Jason

07:10 PM

If the data changes between requests, then yes the pagination will not be consistent across requests

07:10

Jason

07:10 PM

But if the data is consistent, then pagination will be “stable”

Ivy

07:11 PM

Thank you! Good to know. I was thinking of using the server-side caching feature in that case.

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Pagination of Data with Different Page Sizes

Jameshwart inquires about pagination with different page sizes. Jason advises on pagination using 'per_page', 'found', and 'modulo'. Kishore Nallan suggests using 'offset' and 'limit' for flexible pagination.

2mo

Typesense Pagination and Caching Concerns

Michal expressed concerns about Typesense costs and pagination for an infinite scroll app. Kishore Nallan suggested fetching 250 results upfront and mentioned Typesense doesn't cache per page result sets.

7mo

Pagination and Determining Next Page

Gustavo asked about pagination and determining the next page. Jason suggested using the `found`, `per_page`, and `page` keys to calculate the total number of pages.

3mo