Struct RedbBackend 

pub struct RedbBackend { /* private fields */ }

redb-backed StorageBackend.

One redb::Database file per backend instance. All keys share a single "graphrefly" table. Per-write-call ACID transactions (D163).

Example

use std::sync::Arc;
use graphrefly_storage::{redb_backend, snapshot_storage, SnapshotStorageOptions};

let backend = redb_backend("./checkpoints.redb");
let tier = snapshot_storage(backend, SnapshotStorageOptions::<MyState, _>::default());
tier.save(state).unwrap();

Implementations

impl RedbBackend

pub fn new(path: impl AsRef<Path>) -> Result<Self, StorageError>

Open or create a redb database at path.

Errors

Returns StorageError::BackendError if the database file can’t be opened or created (permissions, corrupt file, etc.).

pub fn name_str(&self) -> &str

Diagnostic: the path-derived name (e.g. "redb:./checkpoints.redb").

Trait Implementations

impl Debug for RedbBackend

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl StorageBackend for RedbBackend

fn name(&self) -> &str

Diagnostic name (e.g. "memory", "file:./checkpoints"). Surfaces in error messages and tier Display impls.

fn read(&self, key: &str) -> Result<Option<Vec<u8>>, StorageError>

Read raw bytes; returns Ok(None) on miss.

fn write(&self, key: &str, bytes: &[u8]) -> Result<(), StorageError>

Write raw bytes.

fn delete(&self, key: &str) -> Result<(), StorageError>

Optional delete-by-key. Default is no-op so append-only or read-only backends can stay quiet.

fn list(&self, prefix: &str) -> Result<Vec<String>, StorageError>

Enumerate keys matching prefix (lex-ASC). Empty prefix enumerates all keys. Default returns BackendNoListSupport — backends that don’t support enumeration surface the diagnostic here at first call, NOT at attach (mirrors TS lazy-throw semantics for list_by_prefix).

fn flush(&self) -> Result<(), StorageError>

Optional drain hook — adapter authors implement when buffering writes. Default no-op; tier flush() does NOT cascade into this by default (the tier owns its own buffer; backend buffering is a separate concern the backend author opts into).