Re:Crsql – Multi-writer and CRDT support for SQLite
by bawolff on Tuesday November 15, 2022 @06:11AM
(#33607796)
Sure, but i would kind of expect the readme document to explain what happens (what is the consistency model) since this is not an obscure case but basically the primary use case for an ACID database like sqlite.
Re:Crsql – Multi-writer and CRDT support for SQLite
by anentropic on Tuesday November 15, 2022 @07:11AM
(#33608174)
https://github.com/vlcn-io/cr-sqlite/tree/ca9a67f9050844458e...
It's not very clearly stated, but the links show it has "Last Write Wins" semantics for conflicting changes
https://bartoszsypytkowski.com/crdt-map/#crdtmapwithlastwrit... https://bartoszsypytkowski.com/operation-based-crdts-registe...
Notwithstanding, there are a lot of possible changes that can compose well, but with traditional databases it is hard to merge divergent datasets even if the changes are non-overlapping. That is where solutions like this improve the state of the art - by obviating a need for secondary sync/merge layer on top.
For the actual cell level conflicts the application developer will have to either write custom resolution or model the domain so that they can be resolved by user later.