Supported features
These pages describe the implementation in the repository’s main branch. They are not a claim of complete ISO GQL conformance.
Executable means the database runs the documented form. Partial means specific forms or data types are supported. Syntax only means the parser builds an AST, but the database does not execute that feature.
Database execution
Section titled “Database execution”| Capability | Status | Reference |
|---|---|---|
| Scalar queries, parameters, LET, FOR, FILTER | Executable | Query clauses |
| RETURN, SELECT, ordering and pagination | Executable | RETURN |
| MATCH and OPTIONAL MATCH | Executable | Patterns |
| Quantified edges, path modes, shortest selectors | Partial: resource and unbounded-search restrictions | Quantifiers |
| Repeated groups, alternatives, questioned paths | Partial: binding restrictions | Complex patterns |
| Aggregation, set operations and independent nested queries | Executable | Aggregates |
| Whole-element values, aliases and property lookups | Executable | Element references |
| INSERT, SET, REMOVE, DELETE | Executable on open graphs | Writes |
| Catalog DDL and graph type definitions | Partial: typed graph data access is not implemented | Graph types |
| Sessions and declared parameters | Partial: restricted initializer evaluation | Session parameters |
| Explicit read-only/read-write transactions | Executable | Transactions |
| Arrow import and local Parquet persistence | Executable | Import |
Syntax ahead of execution
Section titled “Syntax ahead of execution”The parser also accepts casts, CASE, most string/numeric functions, temporal expressions, record/path constructors, type/normalization/source/destination predicates, EXISTS/VALUE subqueries, typed LET, procedure calls, NEXT chains and graph-pattern YIELD. Their dedicated reference pages state the restriction next to the syntax.
PATH_LENGTH, ELEMENTS, COALESCE, NULLIF, aggregate functions and the documented element predicates are executable; broad function-family names alone are not a reliable support test.
Operational boundaries
Section titled “Operational boundaries”- Query results are fully materialized; there is no streaming or prepared-statement API.
- Updates rewrite the affected graph; there are no indexes or incremental Parquet deltas.
- Durable storage targets a local Linux/macOS filesystem, not network filesystems or object storage.
- Format v3 has no migration from older formats.
- There is no server protocol, authentication service or distributed transaction coordinator.
Unsupported operations return errors. Successful parsing alone is not an execution or conformance test. See limits before running expensive path searches.