mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-30 23:36:52 +00:00
Jack Ye
ddb318567a
## Summary - Complete the SQL reference: `ATTACH DATABASE`, the `CHANGES` clause, and `dedupe()`/`duplicate_pairs()` (verified against current sophon source; these were recently renamed from `vector_dedup`/`vector_duplicate_pairs`). Fix the blob-column default-projection claim and add the previously undocumented `blob_descriptor()`. - Enrich the gated Functions draft (still `.mintignore`'d, pre-release): chained Functions over blob outputs, GPU-produced blobs, Secrets, multi-input/output binding, `code=[module]` packaging. - Upgrade the materialized-view and computed-column auto-refresh drafts with precise, verified catch-up semantics, and add the missing `ALTER MATERIALIZED VIEW` / `CREATE ... WITH(...)` sections (also gated — the automatic-refresh scheduler is still dev/staging-only). - Thread one running example (video frames → GPU extract/caption → dedup → auto-refreshing materialized view) through Functions, materialized views, and the LeRobotDataset integration guide instead of a separate tutorial. - Rename "LanceDB OSS"/"OSS" to "LanceDB Embedded"/"Embedded" throughout (52 files); activate the existing availability-comparison mechanism on `basics/offerings.mdx` for a full feature-by-feature comparison table.
60 lines
1.8 KiB
Plaintext
60 lines
1.8 KiB
Plaintext
---
|
|
title: "Namespace"
|
|
sidebarTitle: "Namespace"
|
|
description: "CREATE SCHEMA and DROP SCHEMA: the SQL spelling of namespace DDL."
|
|
icon: folder-tree
|
|
keywords: ["namespace", "schema", "create schema", "drop schema", "sql"]
|
|
availability:
|
|
embedded: unavailable
|
|
enterprise: available
|
|
---
|
|
|
|
A [namespace](/management/namespace) is addressed in SQL as a `SCHEMA`, the
|
|
standard's name for the same concept.
|
|
|
|
## CREATE SCHEMA {#create}
|
|
|
|
```sql
|
|
CREATE SCHEMA analytics
|
|
CREATE SCHEMA db1.`ns1$ns2`
|
|
CREATE SCHEMA IF NOT EXISTS `ns1$ns2`
|
|
```
|
|
|
|
A nested namespace is one backtick-quoted name with `$` between its
|
|
components: `` db1.`ns1$ns2` `` creates `ns2` inside `ns1` in database `db1`,
|
|
provided `ns1` already exists. The part before the dot is the database, so a
|
|
three-part path such as `db1.ns1.ns2` is rejected. `public` is the database's
|
|
root namespace, which is never created or dropped.
|
|
|
|
`IF NOT EXISTS` makes the statement a no-op rather than an error when the
|
|
namespace is already there.
|
|
|
|
## DROP SCHEMA {#drop}
|
|
|
|
```sql
|
|
DROP SCHEMA db1.analytics
|
|
DROP SCHEMA IF EXISTS `a$b`
|
|
DROP SCHEMA `a$b` RESTRICT
|
|
```
|
|
|
|
<Warning>
|
|
`CASCADE` is rejected: **"DROP SCHEMA CASCADE is not supported; drop the
|
|
objects inside first."** A namespace's tables, views and other objects must be
|
|
dropped explicitly before the namespace itself can go. `RESTRICT` (the
|
|
default) states that requirement rather than changing it.
|
|
</Warning>
|
|
|
|
## What to read next {#next}
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Database" icon="database" href="/sql/ddl/database">
|
|
Attaching the database a namespace lives in.
|
|
</Card>
|
|
<Card title="Namespace" icon="folder-tree" href="/management/namespace">
|
|
The SDK equivalent, and how a namespace fits the catalog hierarchy.
|
|
</Card>
|
|
<Card title="Table" icon="table" href="/sql/ddl/table">
|
|
Creating tables inside a namespace.
|
|
</Card>
|
|
</CardGroup>
|