Naming rules
Databases, namespaces, tables and views all have names. Choose names that describe their purpose, such asdocuments, prod or training_2026.
Consistent names make data easier to find and application code easier to read.
Use the following rules for names that work across LanceDB Embedded and LanceDB Enterprise.
- Names and individual namespace or database components must not be empty.
- Table, view, namespace and database components cannot be
.or... - Secret names cannot be
.or... - Avoid
$and:because they separate parts of qualified identifiers. - A namespace path beginning with
publiccannot contain another component.
Namespace paths
A namespace path is a list of names.["prod", "search"] identifies the
search namespace within prod. A table named documents belongs to that
namespace; its table name remains documents.
Use the SDK’s namespace-path argument to supply the list. A period inside an
SDK name is a character in that name, not a separator that creates another
namespace. SQL uses its own qualified-name syntax; see
SQL namespace paths.
The empty path [] identifies the root namespace.
Examples
Learn more
- Namespaces: create namespaces and address tables.
- Limits: check other constraints before designing your schema.