cr-sqlite

https://github.com/vlcn-io/cr-sqlite/ > Tables are modeled as GSets... > Rows are currently modeled as LWW maps. I.e., each column in a row is a LWW Register. Multi value registers are also planned - though I'm not sure how that'll be implemented. (One also has the opportunity to see failing writes to the LWW register, so for my app I can (in theory) potentially surface those somewhere to the user as a resolvable conflict.)

All the CRDTs I'm looking at here are doing the work in memory only. Adding a good persistence layer is a big missing piece here. But some people are working on adding CRDTs to sqlite: https://github.com/vlcn-io/cr-sqlite It'd be really fun to see if this approach can be adapted to sqlite's b-tree. But it might not work as-is. The b-tree implementation I have is quite a bit different from most b-trees because I'm storing offsets rather than "keys", and because I'm storing compacted runs of items rather than individual rows. I went into a lot more detail about what it might look like here: https://github.com/vlcn-io/cr-sqlite/issues/65#issuecomment-...

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...

I want to build local first software backed by EdgeDB. Similar to these tools: - https://replicache.dev - https://github.com/tantaman/conflict-free-sqlite - https://aphrodite.sh I wonder if EdgeDB provides any utilities to make this already perhaps? Or community has to build some kind of CRDT software that builds on top of EdgeDB that will do local syncing? Maybe that's planned to be tackled for 3.0?