3 ms·
Does that mean you have to scan the entire results set to get the right page? So if I am on page 100, I have to query pages 1-99 and discard them? Or is there
by erikpukinskis 4y ago
Does that mean you have to scan the entire results set to get the right page? So if I am on page 100, I have to query pages 1-99 and discard them?
Or is there a trick here I’m missing?
- nerdponx 4y agoI think the point is that clients are not even given the option to think in terms of "page numbers". What's the use case for needing the 100th page of a query result, that also doesn't allow you to cache the 100th page locally to retrieve it later?
- imbusy111 4y agoThere are no pages anymore. You fetch a record by ID and next N records.
- erikpukinskis 4y agoRight, but in your database query doesn’t that require you to get a monster result set and filter it down in your application layer? There’s no SQL clause for “WHERE IT WOULD COME AFTER id=ah73d IN THE RESULT SET” as far as I’m aware.