You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: