pub struct DatabaseStorage { /* private fields */ }Implementations§
Source§impl DatabaseStorage
impl DatabaseStorage
pub fn new_in_memory() -> Result<DatabaseStorage>
Sourcepub fn new_temp_file() -> Result<DatabaseStorage>
pub fn new_temp_file() -> Result<DatabaseStorage>
Open operator storage over a private, on-disk temporary database — SQLite’s
"" filename: a per-connection scratch DB created in the temp directory and
deleted automatically when the connection closes. This is the server spill
path: operator state can grow past RAM and overflow to disk, but it keeps the
durability-free scratch pragmas (journal_mode = OFF, synchronous = OFF,
locking_mode = EXCLUSIVE), so there are no journal writes or fsyncs on the
hot path — pages only reach disk when the OS page cache evicts them.
pub fn new(conn: Connection) -> Result<DatabaseStorage>
pub fn with_options( conn: Connection, opts: DatabaseStorageOptions, ) -> Result<DatabaseStorage>
Sourcepub fn create_storage(&self) -> OpStorage
pub fn create_storage(&self) -> OpStorage
Allocate one operator’s isolated keyspace (a fresh op_id) over this database.
The store gets its own (undrained) error sink — for direct use outside a graph
(tests, benchmarks). Inside a graph the [StorageProvider] seam threads the
graph’s runtime_error sink in via create_storage_with_sink.
pub fn checkpoint(&self) -> Result<()>
Trait Implementations§
Source§impl Clone for DatabaseStorage
impl Clone for DatabaseStorage
Source§fn clone(&self) -> DatabaseStorage
fn clone(&self) -> DatabaseStorage
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl StorageProvider for DatabaseStorage
The graph’s StorageFactory vends one OpStorage per stateful operator straight
off the database, threading the graph’s runtime_error sink in (WS02.3) so storage
failures surface via take_runtime_error at the mutation boundary instead of aborting.
impl StorageProvider for DatabaseStorage
The graph’s StorageFactory vends one OpStorage per stateful operator straight
off the database, threading the graph’s runtime_error sink in (WS02.3) so storage
failures surface via take_runtime_error at the mutation boundary instead of aborting.