You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A cache invalidation on a table with no secondary index stores null, so the refill restamps @createdTime #3597
A cache invalidate() (_writeInvalidate with no residency list) on a table with no secondary index stores null as the invalidated value. A later refill reads @createdTime from that value, finds none, and stamps a new created time, so createdAt moves forward on every invalidate → refill cycle. Tables with any secondary index keep the created time on the stub (the source-fill/residency-stub fix carries it forward there).
The null value is relied on: integrationTests/database/record-caching-invalidate uses it as the reachable null-root-value case, and scheduleCleanup removes a null entry as a tombstone after audit retention. Storing { [primaryKey]: id, createdAt } instead changes both. resources/DESIGN.md (residency stubs) records the current behavior.
Activity