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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tanstack/angular-db@0.1.38
Patch Changes
09da081,86ad40c]:@tanstack/db@0.5.12
Patch Changes
Ensure deterministic iteration order for collections and indexes. (#958)
SortedMap improvements:
compareKeysutility toutils/comparison.tsfor reuseBTreeIndex improvements:
CollectionStateManager changes:
SortedMapforsyncedData, ensuring deterministic iteration ordercomparefunction is provided, entries are sorted by key onlyThis ensures that live queries with
orderByandlimitproduce stable, deterministic results even when multiple rows have equal sort values.Enhanced multi-column orderBy support with lazy loading and composite cursor optimization. (#926)
Changes:
or(gt(col1, v1), and(eq(col1, v1), gt(col2, v2)))) for backend optimizationBenefits:
Updated dependencies [
52c29fa]:@tanstack/db-ivm@0.1.14
Patch Changes
Use row keys for stable tie-breaking in ORDER BY operations instead of hash-based object IDs. (#957)
Previously, when multiple rows had equal ORDER BY values, tie-breaking used
globalObjectIdGenerator.getId(key)which could produce hash collisions and wasn't stable across page reloads for object references. Now, the row key (which is alwaysstring | numberand unique per row) is used directly for tie-breaking, ensuring deterministic and stable ordering.This also simplifies the internal
TaggedValuetype from a 3-tuple[K, V, Tag]to a 2-tuple[K, V], removing unnecessary complexity.@tanstack/electric-db-collection@0.2.13
Patch Changes
09da081,86ad40c]:@tanstack/offline-transactions@1.0.2
Patch Changes
09da081,86ad40c]:@tanstack/powersync-db-collection@0.1.16
Patch Changes
09da081,86ad40c]:@tanstack/query-db-collection@1.0.7
Patch Changes
09da081,86ad40c]:@tanstack/react-db@0.1.56
Patch Changes
09da081,86ad40c]:@tanstack/rxdb-db-collection@0.1.44
Patch Changes
09da081,86ad40c]:@tanstack/solid-db@0.1.55
Patch Changes
09da081,86ad40c]:@tanstack/svelte-db@0.1.55
Patch Changes
09da081,86ad40c]:@tanstack/trailbase-db-collection@0.1.56
Patch Changes
09da081,86ad40c]:@tanstack/vue-db@0.0.88
Patch Changes
09da081,86ad40c]: