Skip to content
Source
Sign inSign up
TanStack/db

fix(db): settle subset loads after publication #1769

MergedKyleAMathews(GitHub profile, opens in a new tab)merged 15 commits intomain fromrefs/pull/1769/headmerged by tannerlinsley

Showing 39 changed files with 31 additions and 0 deletions (loading 36).

x
0 of 39 viewed, 39 left
6 additions and 0 deletions.changeset/canonical-demand-identity.mdAdded
View file
@@ -0,0 +1,6 @@
+---
+'@tanstack/db': patch
+'@tanstack/query-db-collection': patch
+---
+​
+Canonicalize equivalent loadSubset queries to one demand identity while preserving observable output aliases, exact projected values, and distinct ordered windows. Query DB now reuses the same canonical identity for its on-demand cache keys.
15 additions and 0 deletions.changeset/settle-subset-after-publication.mdAdded
View file
@@ -0,0 +1,15 @@
+---
+'@tanstack/db': patch
+'@tanstack/db-sqlite-persistence-core': patch
+'@tanstack/electric-db-collection': patch
+'@tanstack/powersync-db-collection': patch
+'@tanstack/query-db-collection': patch
+'@tanstack/rxdb-db-collection': patch
+'@tanstack/trailbase-db-collection': patch
+---
+​
+Settle subset loads only after their committed rows and events are visible. A
+commit receipt now rejects with `AbortError` when cancellation wins before
+application and ignores later aborts. Preserve causal publication,
+cancellation, persistence, and error handling across the affected sync
+adapters.
10 additions and 0 deletionsAGENTS.mdModified
View file