Struct SqliteBackend 

pub struct SqliteBackend { /* private fields */ }

Available on crate feature sqlite-session only.

SQLite-backed session (via rusqlite).

Enabled with the sqlite-session Cargo feature.

Schema

Five tables are created on first open (idempotent):

Table	Purpose
meta	home_dc_id and future scalar values
dcs	One row per DC (auth key, address, flags, …)
update_state	Single-row pts / qts / date / seq
channel_pts	Per-channel pts
peers	Access-hash cache

Granular writes

All SessionBackend extension methods (update_dc, set_home_dc, apply_update_state, cache_peer) issue single-row SQL statements instead of the default load-mutate-save round-trip, so they are safe to call frequently (e.g. on every update batch) without performance concerns.

Implementations

impl SqliteBackend

pub fn open(path: impl Into<PathBuf>) -> Result<Self>

Open (or create) the SQLite database at path.

pub fn in_memory() -> Result<Self>

Open an in-process SQLite database (useful for tests).

Trait Implementations

impl SessionBackend for SqliteBackend

fn save(&self, session: &PersistedSession) -> Result<()>

fn load(&self) -> Result<Option<PersistedSession>>

fn delete(&self) -> Result<()>

fn name(&self) -> &str

Human-readable name for logging/debug output.

fn update_dc(&self, entry: &DcEntry) -> Result<()>

Update a single DC entry without rewriting the entire session.

fn set_home_dc(&self, dc_id: i32) -> Result<()>

Change the home DC without touching any other session data.

fn apply_update_state(&self, update: UpdateStateChange) -> Result<()>

Apply a single update-sequence change without a full save/load.

fn cache_peer(&self, peer: &CachedPeer) -> Result<()>

Cache a peer access hash without a full session save.