Document DB sync prototype scope
This commit is contained in:
parent
b01da7be4b
commit
59c86aba6a
4 changed files with 40 additions and 14 deletions
|
|
@ -194,7 +194,10 @@ advancing its per-peer/per-DB cursor. Compatible remote batches are inserted
|
|||
into the local `crsql_changes` table or view before the cursor advances.
|
||||
Loading/configuring the cr-sqlite extension for real application databases
|
||||
remains the database owner's responsibility; the bootstrap tests use
|
||||
deterministic fixture tables.
|
||||
deterministic fixture tables because this dev environment has no `sqlite3` CLI
|
||||
or cr-sqlite extension artifact. DB sync intentionally does not use CAS-backed
|
||||
snapshots or batch blobs in the prototype. Those become useful when initial
|
||||
catch-up or large batches outgrow the protected control path.
|
||||
|
||||
`geth-kv` currently provides a SQLite-backed local fallback for named KV stores
|
||||
through `kv create/set/get`. `kv set --subject <principal>` evaluates local auth
|
||||
|
|
|
|||
Loading…
Reference in a new issue