-
Notifications
You must be signed in to change notification settings - Fork 7
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
Post-transaction tx-data #11
Comments
Now that I'm thinking about this, @smothers should decide if he wants to support both op-based (CmRDT) and state-based (CvRDT) usage patterns. This issue is only helpful for the op-based side. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Datomic, the transaction result includes
tx-data
, which is a fully-resolved and complete version of the transaction originally submitted (i.e. with tempids resolved, transaction functions applied, maps flattened, etc.).It would be very helpful to include something similar in the result of a CausalBase transaction, e.g. for sending on the wire to other participants with their own local versions of the CRDT.
The text was updated successfully, but these errors were encountered: