Struct SqliteRefTable 

pub struct SqliteRefTable { /* private fields */ }

The sqlite row-CAS twin over the co-tenant git_refs rows (substrate.md §refs, ADR-019 §2) — the atomic realization as the one-transaction home: every GitRefs::apply_updates call runs all its CAS check-and-applies inside one BEGIN IMMEDIATE transaction on the co-tenant connection (the migration-checked schema from substrate/w6-migrations), so two clashing applies — from this process or a co-tenant connection of another — serialize on the row write lock and the loser sees the committed winner (stale info), while an atomic denial rolls its transaction back whole, leaving the rows exactly as they were (POC-O’s demonstrated shapes, DQ-2).

Blocking SQL bridges off the async executor (tokio::task::spawn_blocking) per the composition’s concurrency model; the co-tenant handle’s pinned busy timeout absorbs the cross-process write-lock waits. Construction takes the already-migrated handle (CoTenantSqlite::open runs the migrations) — no construction I/O here.

Implementations

impl SqliteRefTable

pub fn new(handle: CoTenantSqlite) -> Self

Mount the refs row CAS over a co-tenant handle (the same handle the sqlite registry twin consumes).

Trait Implementations

impl GitRefs for SqliteRefTable

fn list_refs<'life0, 'life1, 'async_trait>( &'life0 self, repo: &'life1 RepoRecord, ) -> Pin<Box<dyn Future<Output = Result<Vec<RefLine>, StorageError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait,

Ref listing — advertisement + ls-refs response data (the full set; ref-prefix filtering is wire-side, client-driven).

fn apply_updates<'life0, 'life1, 'async_trait>( &'life0 self, repo: &'life1 RepoRecord, updates: Vec<RefUpdate>, atomic: bool, ) -> Pin<Box<dyn Future<Output = Result<Vec<RefOutcome>, StorageError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait,

One CAS transaction per call — the atomic-correctness home (ADR-013 §7; the substrate row transaction — ADR-019 §2). Runs the per-ref CAS; per-ref denials are outcomes (RefOutcome), not errors (a stale ref is a business result of receive-pack — ADR-013 §7–8).

impl RefRows for SqliteRefTable

The liveness seam’s row read: one ordered query over the co-tenant rows (ORDER BY repo_id, name — the canonical order the fingerprint folds), bridged off the executor like every blocking-SQL leg.

fn snapshot<'life0, 'async_trait>( &'life0 self, ) -> Pin<Box<dyn Future<Output = Result<RefRowsSnapshot, StorageError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

The full canonical snapshot: all repos’ rows, name-sorted, with the fingerprint over the canonical form.