-
Notifications
You must be signed in to change notification settings - Fork 131
feat(db,electric,query): separate cursor expressions for flexible pagination #960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
samwillis
wants to merge
3
commits into
main
Choose a base branch
from
samwillis/cursor-pagination
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+767
−129
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| --- | ||
| '@tanstack/db': patch | ||
| '@tanstack/electric-db-collection': patch | ||
| '@tanstack/query-db-collection': patch | ||
| --- | ||
|
|
||
| Enhanced LoadSubsetOptions with separate cursor expressions and offset for flexible pagination. | ||
|
|
||
| **⚠️ Breaking Change for Custom Sync Layers / Query Collections:** | ||
|
|
||
| `LoadSubsetOptions.where` no longer includes cursor expressions for pagination. If you have a custom sync layer or query collection that implements `loadSubset`, you must now handle pagination separately: | ||
|
|
||
| - **Cursor-based pagination:** Use the new `cursor` property (`cursor.whereFrom` and `cursor.whereCurrent`) and combine them with `where` yourself | ||
| - **Offset-based pagination:** Use the new `offset` property | ||
|
|
||
| Previously, cursor expressions were baked into the `where` clause. Now they are passed separately so sync layers can choose their preferred pagination strategy. | ||
|
|
||
| **Changes:** | ||
|
|
||
| - Added `CursorExpressions` type with `whereFrom`, `whereCurrent`, and optional `lastKey` properties | ||
| - Added `cursor` to `LoadSubsetOptions` for cursor-based pagination (separate from `where`) | ||
| - Added `offset` to `LoadSubsetOptions` for offset-based pagination support | ||
| - Electric sync layer now makes two parallel `requestSnapshot` calls when cursor is present: | ||
| - One for `whereCurrent` (all ties at boundary, no limit) | ||
| - One for `whereFrom` (rows after cursor, with limit) | ||
| - Query collection serialization now includes `offset` for query key generation | ||
| - Added `truncate` event to collections, emitted when synced data is truncated (e.g., after `must-refetch`) | ||
| - Fixed `setWindow` pagination: cursor expressions are now correctly built when paging through results | ||
| - Fixed offset tracking: `loadNextItems` now passes the correct window offset to prevent incorrect deduplication | ||
| - `CollectionSubscriber` now listens for `truncate` events to reset cursor tracking state | ||
|
|
||
| **Benefits:** | ||
|
|
||
| - Sync layers can choose between cursor-based or offset-based pagination strategies | ||
| - Electric can efficiently handle tie-breaking with two targeted requests | ||
| - Better separation of concerns between filtering (`where`) and pagination (`cursor`/`offset`) | ||
| - `setWindow` correctly triggers backend loading for subsequent pages in multi-column orderBy queries | ||
| - Cursor state is properly reset after truncation, preventing stale cursor data from being used |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logging