Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalPagination logic comes in two forms.
If a DB is only capable of loading 1000 rows at a time you must not exceed that. But if your display can only handle 12 at a time...
What you need to do is express the paging requirements from where they each originate and accept that they don't all originate in one place.
Don’t assume the 12 row limitation of your presentation will protect the DB. Presentations change.
Pagination logic comes in two forms.
If a DB is only capable of loading 1000 rows at a time you must not exceed that. But if your display can only handle 12 at a time...
What you need to do is express the paging requirements from where they each originate and accept that they don't all originate in one place.
Pagination logic comes in two forms.
If a DB is only capable of loading 1000 rows at a time you must not exceed that. But if your display can only handle 12 at a time...
What you need to do is express the paging requirements from where they each originate and accept that they don't all originate in one place.
Don’t assume the 12 row limitation of your presentation will protect the DB. Presentations change.
Pagination logic comes in two forms.
If a DB is only capable of loading 1000 rows at a time you must not exceed that. But if your display can only handle 12 at a time...
What you need to do is express the paging requirements from where they each originate and accept that they don't all originate in one place.
