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.21
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/db@0.4.16
Patch Changes
Enable auto-indexing for nested field paths (#728)
Previously, auto-indexes were only created for top-level fields. Queries filtering on nested fields like
vehicleDispatch.dateorprofile.scorewere forced to perform full table scans, causing significant performance issues.Now, auto-indexes are automatically created for nested field paths of any depth when using
eq(),gt(),gte(),lt(),lte(), orin()operations.Performance Impact:
Before this fix, filtering on nested fields resulted in expensive full scans:
eq(date)/eq(dispatchId)filters → heavy “graph run” time on param change #727)After this fix, nested field queries use indexes:
Example:
Index Naming:
Auto-indexes for nested paths use the format
auto:field.pathto avoid naming conflicts:auto:statusfor top-level fieldstatusauto:profile.scorefor nested fieldprofile.scoreauto:metadata.stats.viewsfor deeply nested fieldmetadata.stats.viewsFixes Auto-index not used for simple
eq(date)/eq(dispatchId)filters → heavy “graph run” time on param change #727Fixed performance issue where using multiple
.where()calls created multiple filter operators in the query pipeline. The optimizer now implements the missing final step (step 3) of combining remaining WHERE clauses into a single AND expression. This applies to both queries with and without joins: (#732)This reduces filter operators from N to 1, making chained
.where()calls perform identically to using a single.where()withand().Add paced mutations with pluggable timing strategies (#704)
Introduces a new paced mutations system that enables optimistic mutations with pluggable timing strategies. This provides fine-grained control over when and how mutations are persisted to the backend. Powered by TanStack Pacer.
Key Design:
Core Features:
usePacedMutationsfor easy integration in React applicationsAvailable Strategies:
debounceStrategy: Wait for inactivity before persisting. Only final state is saved. (ideal for auto-save, search-as-you-type)queueStrategy: Each mutation becomes a separate transaction, processed sequentially in order (defaults to FIFO, configurable to LIFO). All mutations are guaranteed to persist. (ideal for sequential workflows, rate-limited APIs)throttleStrategy: Ensure minimum spacing between executions. Mutations between executions are merged. (ideal for analytics, progress updates)Example Usage:
@tanstack/electric-db-collection@0.1.40
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/query-db-collection@0.2.39
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/react-db@0.1.38
Patch Changes
Add paced mutations with pluggable timing strategies (#704)
Introduces a new paced mutations system that enables optimistic mutations with pluggable timing strategies. This provides fine-grained control over when and how mutations are persisted to the backend. Powered by TanStack Pacer.
Key Design:
Core Features:
usePacedMutationsfor easy integration in React applicationsAvailable Strategies:
debounceStrategy: Wait for inactivity before persisting. Only final state is saved. (ideal for auto-save, search-as-you-type)queueStrategy: Each mutation becomes a separate transaction, processed sequentially in order (defaults to FIFO, configurable to LIFO). All mutations are guaranteed to persist. (ideal for sequential workflows, rate-limited APIs)throttleStrategy: Ensure minimum spacing between executions. Mutations between executions are merged. (ideal for analytics, progress updates)Example Usage:
Updated dependencies [
979a66f,f8a979b,cb25623]:@tanstack/rxdb-db-collection@0.1.27
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/solid-db@0.1.38
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/svelte-db@0.1.38
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/trailbase-db-collection@0.1.38
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/vue-db@0.0.71
Patch Changes
979a66f,f8a979b,cb25623]:todos@0.0.17
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/db-example-paced-mutations-demo@0.0.2
Patch Changes
979a66f,f8a979b,cb25623]:@tanstack/db-example-react-todo@0.1.18
Patch Changes
cb25623]: