The SQL contract is the source of truth for implemented syntax and semantics. This page summarizes remaining limitations; it is not a feature commitment or a release schedule.
Derived tables, ordinary CTEs, DATE/DECIMAL, SQL savepoints, DROP TABLE/INDEX, table/column rename, OFFSET, generated integer primary keys and column/star INSERT RETURNING, named parameters, table-level composite keys and mixed/qualified star projections, CHECK, immediate RESTRICT foreign keys, VALUES UPSERT, BLOB, controlled reads, JOIN USING, ROUND and column/star UPDATE/DELETE RETURNING are implemented. Read-only SQL connections can use committed snapshots. Resumable cursors and callback streaming cover scans, OFFSET, UNION ALL, ordered index order and one or two INNER/LEFT/CROSS joins; blocking shapes remain materialized. The pinned 22-query analytical workload has recorded correctness and timing evidence; that does not imply full SQL compatibility or production readiness.
| Area | Limitations |
|---|---|
| Application integration | Streaming three or more joins, RIGHT/FULL joins and derived relations, expressions in RETURNING |
| Query memory | More complete buffer accounting and external sort/group/join spilling; current limits do not cap all allocations |
| Data integrity | Deferred/cascading foreign keys, ADD CONSTRAINT, INSERT SELECT UPSERT and partial conflict targets |
| SQL convenience | NULLS FIRST/LAST and broader scalar/string functions; check the dialect contract before selecting a form |
| Advanced queries | Recursive CTEs, windows and persisted views |
| Generated keys | Sequences or AUTOINCREMENT, which must not reuse a deleted maximum; the current maximum is already remembered until that key disappears |
| Types and indexes | Heterogeneous BLOB values in undeclared columns, collations, broader domain operations and partial/expression indexes |
Cascading/deferred foreign keys, triggers and views are not implemented. General SQLite affinity quirks, its file/C ABI and every PRAGMA are not compatibility targets. Server protocols and users/roles are outside the current embedded-library scope. Optional row paging, snapshot readers and background checkpoints belong to the storage/execution layer. General persisted index pages, cross-process readers, concurrent file owners and Windows support remain separate platform constraints.