docs: Add comprehensive cursor pagination guide #2177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds comprehensive documentation for implementing efficient cursor-based pagination with
Dapper, addressing the common performance issue with OFFSET/FETCH pagination on large datasets.
Why This Matters
Many developers default to OFFSET/FETCH pagination, which becomes exponentially slower as users
navigate deeper into results. This guide demonstrates how cursor pagination maintains O(1)
performance regardless of page depth.
What's Included
Performance Impact
Based on production experience with tables containing millions of rows:
Testing
References
This addresses community discussions about pagination performance and provides a comprehensive
solution that many have been implementing independently.
Looking forward to your feedback!