docs: keep the stable-row-id caveat for deployments

The earlier change dropped every statement that a materialized view's
source needs stable row ids, because main no longer requires them. That
holds for the local SDK only. Sophon main creates a view through SQL by
default with the creation checks of its pinned lancedb (00f5dd6f), which
predates #4373 and still rejects a source without stable row ids.

The refresh and management pages now say a local view needs no special
source and a deployment may still require stable row ids, and the
architecture, limits, table and database pages note that requirement.
The summaries say a refresh brings a view up to date instead of saying
it recomputes it, since a deployment may reconcile changes rather than
rebuild.
This commit is contained in:
Brendan Clement
2026-10-06 21:09:53 -07:00
parent 0e9dc14d01
commit 305dffe27b
9 changed files with 42 additions and 30 deletions
+1 -1
View File
@@ -38,5 +38,5 @@ are runnable in Colab; the rest are written up here.
| [Multi-vector search](/search/vector-search) | Several embeddings per document. |
| [Reranking](/reranking) | Reordering results to improve the top-k. |
| [Feature engineering](/feature-engineering) | Deriving columns and tables from data already stored. |
| [Materialized views](/management/materialized-view) | A table defined by a query, recomputed by each refresh. |
| [Materialized views](/management/materialized-view) | A table defined by a query, brought up to date by each refresh. |
| [Training](/training/data-loading) | Reading a table into a data loader. |