In-Memory Catalog
The host publishes schemas, tables, columns, scanner settings, file URIs, and view SQL.
metadata → tables + views
Browser-only metadata catalog
Publish metadata.
Query remote files.
Application-owned schemas, tables, and views become an ordinary read-only DuckDB catalog. Tables explicitly declare how their files should be scanned, while views keep reusable SQL definitions close to the metadata.
DuckDB-Wasm
Read-only catalog
Explicit scanners
SQL views
Direct HTTPS
Architecture
The catalog describes tables and views. DuckDB reads the data.
DuckDB-Wasm
SQL can read tables from their declared files or reuse a view definition registered by the catalog.
SQL → table scanner or view
Live demo
Configure the catalog. Run a query.
Environment
Starting
Runtime & hosted file
Resources used by this browser session.
Hosted demo file
Waiting
In-Memory Catalog
Waiting
Hosted demo file
data/demo.parquet
Parquet
- URL
- Loading…
- Rows
- —
- Size
- —
- Columns
- —
- Content SHA-256
—
Catalog
Published metadata
Edit table schemas, scanner configuration, view definitions, and file references that DuckDB sees.
Query
DuckDB table or view query
Waiting for runtime
Examples
Load a query
Click an example to replace the SQL editor contents.
Waiting for the runtime to become ready.
Output
—
Query result
Runtime diagnostics
Diagnostics will appear here after the query.