Expand description
In-memory Lora database — the database-facing orchestration layer.
lora-database owns the parse → analyze → compile → execute pipeline
and exposes a single Database entry point that transports (HTTP,
benches, examples, embedded callers) can drive without knowing about the
underlying crates.
§Quick start
use lora_database::Database;
let db = Database::in_memory();
db.execute("CREATE (:User {name: 'alice'})", None).unwrap();Structs§
- Database
- Owns the graph store and orchestrates parse → analyze → compile → execute.
- Database
Name - Validated logical database name/path.
- Database
Open Options - Options for opening a named filesystem-backed database.
- Execute
Options - InMemory
Graph - Query
Stream - Owning row stream returned by
crate::Database::streamand transaction streaming methods. - Row
- Snapshot
Meta - Metadata reported by
save_snapshot/load_snapshot. Kept small and stable so callers can log / diff it without reflecting on the payload. - Transaction
- Explicit transaction over the in-memory graph.
- WalStatus
- Snapshot of WAL state returned by
WalAdmin::wal_status.
Enums§
- Database
Name Error - Lora
Value - Query
Result - Result
Format - Snapshot
Error - Errors produced by the snapshot codec.
- Sync
Mode - Durability mode for committed transactions.
- Transaction
Mode - Transaction execution mode.
- WalConfig
- Configuration for opening a
Wal.
Constants§
- DEFAULT_
DATABASE_ MAX_ BYTES - Hard ceiling for one portable database archive/root.
Traits§
- Query
Runner - Minimal abstraction any transport can depend on to run Lora queries.
- Snapshot
Admin - Storage-agnostic admin surface for HTTP / binding callers that want to drive snapshot operations without naming the backend type parameter.
- Snapshotable
- A backend that can serialize its state to a byte stream and restore from one.
- WalAdmin
- Storage-agnostic admin surface for the WAL.