Files
lancedb/nodejs/lancedb
Wyatt Alt d96151c385 feat: cascade option on materialized view refresh
A view over a view could only be brought fully up to date by refreshing
each view in the lineage by hand, in order. `cascade` on the refresh
builder, Python `refresh`/`refresh_async` and Node `refresh` does that in
one call: every upstream view is refreshed furthest first, each reading
the version the one before it left, then the named view. `full` applies
to the named view only.

Locally the lineage is walked through each view's source, and each hop is
refreshed against the incarnation read in that walk. Remote tables send
`cascade` in the refresh request, only when set, so older servers that
reject unknown fields are unaffected by plain refreshes.
2026-09-24 19:09:12 +00:00
..
2026-09-23 15:09:40 +08:00
2026-09-09 15:33:04 +08:00
2026-09-09 15:33:04 +08:00
2026-09-09 15:33:04 +08:00
2026-09-23 15:09:40 +08:00