-
-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CausalLog CRDT #321
Comments
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://vlcn.io/blog/crdt-substrate outlines how to create a causal log and traverse it so all peers have the same state.
Now that I'm finally implementing #181 today so users can declare CRRs via:
we can start adding more CRDT types to back tables.
E.g.,
CausalLog would be a nice way to back tables as it gives us a better audit trail and the user some extra flexibility on merge semantics.
Implementation
We can do it two ways (maybe we even support both).
One way --
which creates:
and a view? or vtab? to do a deterministic traversal of events.
The onus is on the user to create event types and process them to build current state. Given that, maybe we only provide a log structure and nothing about the base item table.
Other way --
We could come up with the events ourselves in a similar way to sqlite.org/undoredo.html
The text was updated successfully, but these errors were encountered: