Apply compatible DB sync batches
This commit is contained in:
parent
f7f14f6b27
commit
43433dbf1d
8 changed files with 185 additions and 26 deletions
|
|
@ -151,10 +151,12 @@ extract read-only typed change batches from `crsql_changes` with schema metadata
|
|||
through `db changes`. As a staged network path, `geth db sync <node-id> <name>`
|
||||
uses the protected Iroh control ALPN to request remote typed change batches when
|
||||
the caller has `db.sync` on the remote `resource:db:<name>`. The requester
|
||||
checks remote schema metadata against its local DB before advancing its
|
||||
per-peer/per-DB cursor. Loading cr-sqlite and applying remote changes through
|
||||
`crsql_changes` are future work; the current path exchanges and cursors changes
|
||||
but does not mutate the local application database.
|
||||
checks remote schema metadata against its local DB before applying changes and
|
||||
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.
|
||||
|
||||
`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