Structs§
- A canonical description of all database updates to be applied. Note: this struct can be migrated to an enum if we ever have a need for database-wide batch changes (see
PartitionDatabaseUpdates
enum). - A database-level key of an entire partition. Seen from the higher-level API: it represents a pair (RE Node ID, Module ID). Seen from the lower-level implementation: it is used as a key in the upper-layer tree of our two-layered JMT.
- A database-level key of a substate within a known partition. Seen from the higher-level API: it represents a local Substate Key. Seen from the lower-level implementation: it is used as a key in the Substate-Tier JMT.
- A canonical description of specific Node’s updates to be applied. Note: this struct can be migrated to an enum if we ever have a need for Node-wide batch changes (see
PartitionDatabaseUpdates
enum).
Enums§
- An update of a single substate’s value.
- A canonical description of specific Partition’s updates to be applied.
- A change applied to a Substate - see
PartitionDatabaseUpdates::get_substate_change
. Technically, this is a 1:1 counterpart ofDatabaseUpdate
, but operating on references.
Traits§
- A write interface between Track and a database vendor.
- A partition listing interface between Track and a database vendor.
- A read interface between Track and a database vendor.
Type Aliases§
- A fully-specified key of a substate (i.e. specifying its partition and sort key).
- A raw substate value stored by the database.
- A key-value entry of a substate within a known partition.