From a2803e1a022feea81af603b6ceb35e48441cbe6e Mon Sep 17 00:00:00 2001 From: Brendan Clement Date: Mon, 5 Oct 2026 15:00:20 -0700 Subject: [PATCH] docs: scope the materialized-view note to the SDK it was tested on The note dated the new behavior to "SDK 0.40", but it was verified on the development SDK 0.40.0b12 built from main, and no stable 0.40 has been released. The note now names that build and keeps the comparison with the published 0.39.0, which creates the view empty, has no with_no_data, and writes both matching rows on the first refresh. --- docs/web/feature-engineering/materialized-views.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/web/feature-engineering/materialized-views.mdx b/docs/web/feature-engineering/materialized-views.mdx index c5b86d392..cccab85da 100644 --- a/docs/web/feature-engineering/materialized-views.mdx +++ b/docs/web/feature-engineering/materialized-views.mdx @@ -37,9 +37,10 @@ reach the view through a refresh: -The view is computed on creation from SDK 0.40. In 0.39 and earlier, -`create_materialized_view` always creates the view empty and the first -`refresh()` writes every matching row, two in this example. +These results were verified with the development SDK 0.40.0b12, built from +lancedb main. With the published 0.39.0, `create_materialized_view` creates the +view empty and has no `with_no_data`, so the first `refresh()` writes every +matching row, two in this example. `select` takes column names, `(alias, expression)` pairs, or a dict of the same.