Files
lancedb/docs/web/sql/show.mdx
T
Jack Ye 5b5ed930ac docs: restructure Documentation around one axis, promote the SQL reference
Every group now answers exactly one question. Get started and Concepts cover
what the system is; the verb groups cover doing something with it; Operate,
Secure and Deploy cover running it; SQL reference is lookup. Maintenance becomes
Operate, Governance becomes Secure, and the rest take verbs to match.

Three new pages in Concepts and Get started:

Guarantees states what a write promises when it returns, which version a reader
sees, what survives a failure, and -- the half usually missing -- what is not
guaranteed: no multi-table transactions, no read-your-writes across processes
without an interval, unenforced primary keys that do not enforce, no background
compaction.

Limits collects bounds that were stated in passing across a dozen pages, with
the numbers verified against the code rather than inferred: name lengths, job
event caps, SHOW ERRORS bounds, the sampling range that is refused rather than
clamped.

Architecture illustrates embedded against distributed as the one deployment
decision, and is written to cover both rather than only Enterprise.

Indexing splits by question. Choosing an index is a Query decision and moves
there; building, repairing and GPU-building it stay in Operate.

SQL becomes a top-level reference of fifteen pages instead of a sub-group of
Query. Auditing sophon-sql turned up a large undocumented surface: ALTER TABLE
ADD COLUMN in its plain, computed and function forms with FILTER, IGNORE NULLS
and OVER modifiers; SET UNENFORCED PRIMARY KEY; SET and UNSET WAL with sharding;
CREATE FUNCTION with its dependency options; REFRESH COLUMN and REFRESH
MATERIALIZED VIEW; and the SHOW family. None of it was written down.
2026-09-13 23:32:15 -07:00

88 lines
2.2 KiB
Plaintext

---
title: "SHOW"
sidebarTitle: "Show"
description: "Listing jobs, functions, materialized views, and the errors a job produced."
icon: list
keywords: ["show jobs", "show functions", "show materialized views", "show errors", "show tables"]
---
<Badge color="red">Enterprise</Badge> [SQL runs on a deployment.](/sql)
Introspection. `SHOW TABLES` is DataFusion's; the rest are LanceDB extensions
covering objects DataFusion has no concept of.
## SHOW TABLES {#tables}
```sql
SHOW TABLES
```
Lists the tables the session can see.
## SHOW MATERIALIZED VIEWS {#materialized-views}
```sql
SHOW MATERIALIZED VIEWS
```
<Note>
Cheaper than the SDK equivalent. `list_materialized_views` finds views by
reading every table's schema, costing one open per table; this asks the server.
</Note>
## SHOW FUNCTIONS {#functions}
```sql
SHOW FUNCTIONS
```
Lists registered [functions](/management/function) and their versions. Since a
version is immutable and a column pins the version that fills it, this is how
you find which versions are still in use before dropping one.
## SHOW JOBS {#jobs}
```sql
SHOW JOBS
```
Every job the server knows about — id, type, state, creation time. The SQL
counterpart of `list_jobs`; see [Query and job](/basics/jobs).
## SHOW ERRORS {#errors}
```sql
SHOW ERRORS ON <table> [FOR JOB '<job-id>'] [LIMIT <n>]
```
```sql
SHOW ERRORS ON documents
SHOW ERRORS ON documents FOR JOB 'job-abc' LIMIT 100
```
Why rows failed. This is the statement to reach for when a
[refresh](/sql/refresh) reports fewer filled rows than you expected.
**Errors and limits**
| | |
| --- | --- |
| `LIMIT` | must be between 1 and 100,000 |
| Failed jobs scanned without `FOR JOB` | 32 most recent |
| Tables the server does not open directly | not supported |
Without `FOR JOB` this surveys recent failures and stops at 32 jobs. When the
listing stops at your `LIMIT`, the message says so — narrow with `FOR JOB`
rather than raising the limit blindly.
## See also {#see-also}
<CardGroup cols={2}>
<Card title="Management" icon="folder-tree" href="/management">
The SDK listing calls, per object.
</Card>
<Card title="Query and job" icon="hourglass-half" href="/basics/jobs">
What a job handle exposes beyond these listings.
</Card>
</CardGroup>