Skip to main content

Crate uqa_storage_redb

Crate uqa_storage_redb 

Source
Expand description

Pure-Rust redb implementation of UQA’s ordered Key/Value storage contract.

RedbStorage owns one database and implements uqa_storage::PersistentStorageProvider. Every opened engine session gets an independent RedbKeyValueStore transaction state while sharing the same MVCC database.

Structs§

RedbKeyValueStore
A provider-independent session with pinned reads and conditional atomic publication. Common storage resolves typed index changes before physical admission; SQL isolation and tuple locks remain above this byte-record contract.
RedbRecordStore
Physical record persistence over one shared redb file owner. Reads retain logical sequence boundaries, and native writers exist only inside allocation, commit and abort calls.
RedbStorage
Shared redb database owner and engine-session factory.
VersionedSessionOptions
Retention allowance for one logical session, including private history, savepoints, batches and retained views. Once more than half of it is used, the private changes of a transaction move into sorted runs in encrypted temporary files, so the size of a transaction is bounded by disk; a single value or batch that does not fit in it is still an error.