Skip to content
Source
Sign inSign up
TanStack/db

fix(db): explain orderBy index fallback causes #2196

MergedKyleAMathews(GitHub profile, opens in a new tab)merged 10 commits intomain fromrefs/pull/2196/headmerged by KyleAMathews(GitHub profile, opens in a new tab)

Showing 12 changed files with 209 additions and 4 deletions (loading 9).

x
0 of 12 viewed, 12 left
5 additions and 0 deletions.changeset/curly-oranges-explain.mdAdded
View file
@@ -0,0 +1,5 @@
+---
+'@tanstack/db': patch
+---
+​
+Explain whether bounded `orderBy` queries lack a field index, have mismatched comparison options, or have an index that cannot support ordered lazy loading.
33 additions and 4 deletionsdocs/contributing/oracle-coverage.mdModified
View file
@@ -279,6 +279,15 @@
rank-and-membership departure rollback are adjacent controls. After an
acknowledged marker departure, restoring that marker must restore both rows
and its Collection or Effect publication.
+Its held-load grammar also replays an unindexed descending joined window in
+which an installed null-ranked row fills the visible window beyond the settled
+provider prefix. After earlier deletes and held answers, the owner compares
+public rows with an independent full-source sort; a boundary-blind refill check
+leaves the next eligible filler row unseen and fails at the final checkpoint.
+For signalling refetches, the no-new-full-source work assertion applies to
+indexed numeric orders with finite ranks. Unindexed underfilled continuations
+and unexpressible null or NaN boundaries may use full-source recovery; the
+owner checks their row law but does not claim bounded transfer for them.
​
At the immediate cut, both consumers must publish the recomputed installed-row
window, even if it is short. Missing extent must start a useful finite