Structs§
- Buffered
RowSource - Buffered cursor backed by a pre-computed
Vec<Row>. Used both as a simple “rows already collected” adapter and as the leaf fallback for operators whose internals still require full materialization. - Combined
Result - Combined
Row - Execute
Options - Execution
Context - Executor
- Graph
Result - Hydrated
Graph - Hydrated
Node - Hydrated
Relationship - Lora
Path - A materialised path: alternating node/relationship IDs. nodes.len() == rels.len() + 1
- Mutable
Execution Context - Mutable
Executor - Mutable
Pull Executor - Pull-based read-write executor. Wraps the existing
MutableExecutorunder the same row-cursor API. Mutations are applied duringopen_compiled; the returned cursor yields the resulting rows lazily. - Pull
Executor - Pull-based read-only executor.
- Row
- RowArrays
Result - Rows
Result
Enums§
- Executor
Error - Lora
Value - Property
Conversion Error - Errors that can arise when converting a
LoraValueinto aPropertyValuefor storage on a node or relationship. - Query
Result - Result
Format - Stream
Shape - Classification of a compiled query, used by the database layer to
decide whether
db.streamneeds a hidden staged transaction.
Traits§
- RowSource
- Fallible pull-based row cursor.
Functions§
- classify_
stream - Classify a compiled query for streaming. Treats any UNION branch
the same as the head: a single mutating op anywhere across the
compiled query promotes the whole query to
Mutating. - collect_
compiled - Drain a freshly opened cursor into a
Vec<Row>. Convenience for callers that want the streaming entry point but a buffered result. - compiled_
result_ columns - Result column names for a compiled query (head plan; UNION branches must produce the same shape so the head’s columns are authoritative).
- drain
- Drain a row source into a
Vec<Row>, propagating the first error. - lora_
value_ to_ property - Fallible conversion used on every write path
(
set_property_from_expr,overwrite_entity_target,mutate_entity_target,eval_properties_expr, plus CREATE / MERGE). Rejects VECTOR values nested inside lists at any depth — everything else falls through to the infallibleFromimplementation above. A top-level VECTOR property is always fine; only LISTs that directly contain a VECTOR entry are rejected. - plan_
result_ columns - Result column names derived from the compiled plan.
- project_
rows - value_
matches_ property_ value