Re:GraphQL Is a Trap?
by marcosdumay on Friday May 06, 2022 @02:38PM
(#31288431)
The server side of pagination is really complex if you want to make sure all the results are returned exactly once. If that's your case, consider not paginating at all.
But very often, a result missing or duplicated in a few queries isn't a showstopper. On that case, pagination is very simple.
Spring Batch covers the cases where you have to get the right answer!
That is you are "full scanning" and making a report or doing something like a reconciliation process in a financial institution, it is not like some image boards where there is a link to the 1781th page of images but it spends forever loading it if you click on it.
Most of the simple ways of doing it with SQL are problematic. In these docs
https://docs.spring.io/spring-batch/docs/current/reference/h...
there is some discussion of the problems and some answers that go back to the mainframe era.