SQL reference
Executable SQL surface for the current single-node NYXDB engine.
This reference documents statements accepted by the current parser and engine. It deliberately separates implemented SQL from experimental and unsupported surfaces. Accepted architecture decisions and future grammar are not presented as runtime features.
The authoritative release inventory is the
engine capability matrix.
Use SHOW FUNCTIONS and SHOW TABLES to inspect a running revision.
Statement map
| Area | Current surface |
|---|---|
| Schema | CREATE TABLE, inline indexes, views, materialized views, streams, transforms, and storage topology |
| Data | INSERT, UPDATE and DELETE for keyed state, plus block ingest |
| Queries | CTEs, subqueries, joins, aggregation, set operations, ordering, limits, temporal and streaming prefixes |
| Application access | Experimental auth providers, typed read-only endpoints, application grants, and query-driven rate limits |
| Inspection | SHOW, DESCRIBE, EXPLAIN, system tables, and CANCEL QUERY |
| Lifecycle | ALTER for supported objects and DROP with dependency checks |
Create tables
Columns, keys, attributes, indexes, and required settings.
Query data
SELECT clauses, aggregation, CTEs, and set operations.
Join data
Relational, ASOF, and latest-per-key joins.
Stream results
Snapshot, historical replay, windows, and emission policies.
Application access
Define auth providers, published endpoints, view grants, and per-user rate limits.
Inspect the engine
SHOW, DESCRIBE, EXPLAIN, and runtime controls.
Function catalog
Discover and use the executable function inventory.
Conventions
- Keywords are shown in uppercase for readability; parsing is case-insensitive.
- Examples name
storage_policyexplicitly because it is required when a table is created. - Features whose compatibility contract may change are labeled Experimental.
- A statement documented as unsupported is rejected explicitly; do not depend on parser acceptance in a future build without checking that release.
The server accepts one statement per request. A trailing semicolon is allowed. Multi-statement transactions and MVCC are not available.