mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-10-08 03:10:26 +00:00
Document BlobBackend as a transitional enum
Mark the Slate arm as temporary and record that the SQLite arm's verified-read and hash-conflict semantics are the intended end state, so the dual-backend enum reads as a rollout vehicle rather than a permanent abstraction. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
cc16362528
commit
01efe7c883
1 changed files with 8 additions and 1 deletions
|
|
@ -33,6 +33,14 @@ impl Record for Blob {
|
|||
}
|
||||
}
|
||||
|
||||
/// Which storage engine holds the blobs.
|
||||
///
|
||||
/// This enum is a transition vehicle, not a permanent abstraction: `Slate`
|
||||
/// preserves current production behavior while the SQLite backend rolls out.
|
||||
/// Once runtime blob storage switches to SQLite and legacy blobs are
|
||||
/// imported, delete the `Slate` arm (and this enum) and inline the SQLite
|
||||
/// implementation into [`BlobStore`]. The SQLite arm's semantics — verified
|
||||
/// reads and loud failure on hash conflicts — are the intended end state.
|
||||
enum BlobBackend {
|
||||
Slate(Repository<Blob>),
|
||||
Sqlite(SqlitePool),
|
||||
|
|
@ -140,7 +148,6 @@ impl BlobStore {
|
|||
}
|
||||
}
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
#[cfg(test)]
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue