reifydb-engine 0.5.6

Query execution and processing engine for ReifyDB
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

// SPDX-License-Identifier: Apache-2.0
// Copyright (c) 2025 ReifyDB

//! Virtual machine that executes the instruction stream emitted by the planner. The VM owns the per-request
//! lifecycle (admin, command, query, subscription), threads parameters through, walks the plan, dispatches each
//! instruction to its handler, and returns the resulting columns or change deltas to the caller.
//!
//! Instruction handlers live alongside the VM so the dispatch table is the single place that decides what an
//! opcode does. Adding a new instruction means writing a handler and wiring it in - planner output never reaches
//! storage without first being interpreted here.

use reifydb_type::params::Params;

#[derive(Debug)]
pub struct Admin<'a> {
	pub rql: &'a str,
	pub params: Params,
}

#[derive(Debug)]
pub struct Command<'a> {
	pub rql: &'a str,
	pub params: Params,
}

#[derive(Debug)]
pub struct Query<'a> {
	pub rql: &'a str,
	pub params: Params,
}

#[derive(Debug)]
pub struct Subscription<'a> {
	pub rql: &'a str,
	pub params: Params,
}

#[derive(Debug)]
pub struct Test<'a> {
	pub rql: &'a str,
	pub params: Params,
}

pub(crate) mod exec;
pub mod executor;
pub mod instruction;
pub mod services;
pub mod stack;
#[allow(clippy::module_inception)]
pub mod vm;
pub mod volcano;