Expand description
Query execution.
The executor turns a planned access path into concrete catalog operations.
parsed statement
+
chosen access path
|
v
executor node
|
+--> table cursor scan
+--> rowid lookup
+--> PK index -> rowid -> table lookup
+--> secondary index -> rowid set -> table lookupThis layer should stay storage-agnostic at the page level. If a change here requires knowledge of B-tree node layout or pager internals, the boundary below catalog has started to leak.
Re-exports§
pub use crate::query::runtime::ExecutionContext;pub use crate::query::runtime::MutationEvent;pub use crate::query::runtime::QueryExecutor;pub use crate::query::runtime::QueryResult;
Structs§
- Alter
Executor - Create
Executor - Create
Index Executor - Delete
Executor - Drop
Executor - Drop
Index Executor - Insert
Executor - Select
Executor - Update
Executor