19 releases (6 breaking)

new 1.0.0-rc2 Dec 13, 2024
1.0.0-rc1 Nov 6, 2024
0.12.0 Oct 4, 2024
0.10.1 Jun 28, 2024
0.7.3 Nov 8, 2023

#1461 in Database interfaces

Download history 20/week @ 2024-08-26 144/week @ 2024-09-02 9/week @ 2024-09-09 35/week @ 2024-09-16 9/week @ 2024-09-23 221/week @ 2024-09-30 27/week @ 2024-10-07 6/week @ 2024-10-14 9/week @ 2024-10-21 125/week @ 2024-11-04 8/week @ 2024-11-11 16/week @ 2024-11-18 7/week @ 2024-11-25 13/week @ 2024-12-02 111/week @ 2024-12-09

148 downloads per month
Used in 4 crates (via spacetimedb-core)

Custom license

145KB
3K SLoC

Abstract Virtual Machine for execution of end-user logic

It optimizes the code & include a more general "query planner"

The execution is split in 3 "phases":

1- AST formation

Generate the AST (that could be invalid according to the semantics).

This step is outside the [vm] and can be done, for example, by the SQL layer.

Use [dsl] to build the [expr:Expr] that build the AST.

2- AST validation

Calling eval::optimize verify the code has the correct semantics (ie: It checks types, schemas, functions are valid, etc.), and "desugar" the code in a more optimal form for later execution.

This build expr::Expr that is what could be stored in the database, ie: Is like bytecode.

3- Execution

Run the AST build from expr::Expr. It assumes is correct.

Dependencies

~14MB
~266K SLoC