[sundy-li]

Summary

Documents databendlabs/databend#20906 in one existing EN/CN materialized-view reference pair. Adds a short cross-database workflow, not a separate guide.

• A materialized view and its source can use different databases in the same default catalog. Qualify the source; an unqualified name resolves in the session database.
• Add one paired CREATE/REFRESH example. Both source and target databases must already exist.
• Explain dropped-source-database invalidation, restoring the original database with UNDROP, and why creating a same-named replacement does not restore source identity. A dropped materialized-view database does not prevent source-table queries.
• Retain all original examples, the verified v1.2.934 introduction marker, and the complete recently merged SELECT-authorization section. No unrelated translation, lifecycle-internals tutorial, moved-table workaround or withdrawn scope.

Version: Unreleased. Exact source merge f004c938f48fae3bb7042959e2eaddb359c96337 is ahead26/behind0 of the latest observed v1.2.960-nightly tag. No release version was guessed.

Validation

• npm run build:en
• npm run build:cn
• Parse both actual built reference HTML pages: unique cross-database anchor, SQL, diagnostic, original version, and preserved authorization content.
• Exact bounded-addition check: all pre-existing prose, fenced examples and version markers are byte-preserved in each locale. New SQL is identical in EN/CN.
• git diff --check; only two matching reference files changed.
• Inspect all eight changed files at the exact GitHub source merge and its logic fixtures; validate release ancestry through the GitHub commit comparison API.
• First EN build rejected Markdown custom-heading syntax; changed only the two new headings to native MDX-compatible h3 id elements, then reran both full builds and rendered checks successfully.
• No live SQL, CREATE/REFRESH/UNDROP, query rewrite, Rust/unit/logic tests, security tests or benchmarks were run by the agent. Source-author test claims and fixture inspection are not agent runtime-test results. Documentation/static/render validation is not runtime proof.
• Current-head GitHub CI must finish independently. Source-author review requested once; no approval or safe-merge claim.

AI assistance

• AI usage: An AI coding agent inspected exact merged source/static fixtures, drafted only this EN/CN subsection, and ran documentation builds/static/rendered-HTML checks.
• Responsible human on the submitter side: @sundy-li (task owner and docs PR account). The reviewer is not being represented as the submitter-side responsible human.
• The responsible human has read every line of this diff and can explain each change.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Nov 5, 2026 3:46am UTC
docs-cn	Ready	Preview	Nov 5, 2026 3:46am UTC