Views

Applies to: Embedded ❌, Enterprise ✅ A view saves a query that you can refer to by name. Reading the view executes that query against the source tables, using their read-consistency behavior. Views do not store a separate copy of the result. It is the counterpart to a materialized view, which stores rows and is brought up to date by a refresh. Both are catalog objects defined by a query; choose a materialized view when you need to store and reuse the result.

	View	Materialized view
Stores	the query	the rows
Freshness	follows source-table reads	as of the last refresh
Read cost	executes the saved query	queries the stored result
Write cost	none	a refresh

Views are created in LanceDB Enterprise, either in SQL over the Flight SQL endpoint or with the SDKs’ create_view / createView, which send the query to the deployment. Either way, the deployment must have views enabled. See View for CREATE VIEW, DROP VIEW, and listing.

Privileges

A view’s OWNERSHIP and SELECT are granted through the REST ACL API or SQL GRANT/REVOKE:

GRANT SELECT ON VIEW dashboard TO ROLE analysts

See Privileges for the full statement syntax and every target it reaches.

Introduction

Getting Started

Concepts

Data Ingestion

Search

Data Curation

Feature Engineering

Training

Management

Maintenance

Security

Deployment

SQL Reference

Privileges

​Privileges

Privileges