Supported
The form is implemented and has executable evidence.
RadixDB 1.1 development
Current status, without the marketing fog
Version 1.1 is under development. A feature enters the public contract only after targeted checks pass on a pinned revision.
1.1
Not an accepted release
Interfaces and syntax in developing layers may change. For production workloads, wait for a published release and its migration guide.
SQL contract
How feature status works
Limited
A defined subset works; boundaries are documented in its chapter.
Rejected
The engine intentionally returns a verified error.
Version 1.1
Already in the verified contract
- DDL and transactional DDL
- INSERT / UPDATE / DELETE RETURNING
- INNER / LEFT / RIGHT / FULL / CROSS JOIN
- GROUP BY, HAVING, and aggregates
- Subqueries and non-recursive CTEs
- Window functions
- READ COMMITTED and SNAPSHOT
- SAVEPOINT / ROLLBACK TO / RELEASE
- Foreign-key navigation
- BTREE, HASH, BITMAP, and partial indexes
Evidence
Performance always comes with context
RadixDB results are published with the revision, dataset size, hardware, cache state, and workload. A number without those conditions is not treated as evidence.
10M / 100Mreproducible datasets
Cold / warmseparate measurement modes
PG paritycomparable SQL slices
Crash gatesrecovery checks
Verify the contract yourself
The SQL matrix links every capability to its manual chapter and executable test.