Expand description
Common models for state changes in RE
Structs§
- State
Updates - A tree-like description of all updates that happened to a stored state, to be included as a part
of a transaction receipt.
This structure is indexed (i.e. uses
IndexMaps whereVecs could be used) for convenience and performance, since both the source (i.e. Track) and the sink (i.e. Database and API) operate on indexed structures too. This structure maintains partial information on the order of operations (please see individual fields for details), since the end users care about it. Please note that this means multiple instances ofStateUpdatescan represent the same transform of state store (i.e. differing only by order of some operations), and hence it is not 100% “canonical form”.
Enums§
- Batch
Partition State Update - A description of a batch update affecting an entire Partition.
- Database
Update - An update of a single substate’s value.
- Database
Update Ref - A 1:1 counterpart of
DatabaseUpdate, but operating on references. - Node
State Updates - A description of all updates that happened to a state of a single Node. Note: currently, we do not support any Node-wide changes (e.g. deleting entire Node); however, we use an enum for potential future development.
- Partition
State Updates - A description of all updates that happened to a state of a single Partition.
Type Aliases§
- DbSubstate
Value - A raw substate value stored by the database.