Expose db change batches over control
This commit is contained in:
parent
8ffe1d714c
commit
a44eef3126
8 changed files with 130 additions and 15 deletions
|
|
@ -120,9 +120,9 @@ Roadmap items should be actionable and checkable:
|
|||
`cas cleanup` evicts unpinned blobs while retaining pinned blobs.
|
||||
- DB resources can be registered locally and report local-only status plus a
|
||||
read-only SQLite schema summary/hash and `crsql_changes` metadata when
|
||||
present. The DB crate can extract typed read-only `crsql_changes` batches for
|
||||
future sync messages. cr-sqlite loading, applying remote changes, and sync are
|
||||
still roadmap work.
|
||||
present. The DB crate and daemon can extract typed read-only `crsql_changes`
|
||||
batches through `geth db changes` for future sync messages. cr-sqlite loading,
|
||||
applying remote changes, and sync are still roadmap work.
|
||||
- KV stores support local SQLite-backed create/set/get. Iroh Documents
|
||||
replication and command-level prefix-capability enforcement are still roadmap
|
||||
work. The auth evaluator already understands `kv.write_prefix:<prefix>`
|
||||
|
|
|
|||
Loading…
Reference in a new issue