Module holochain_state::mutations [−][src]
Enums
Functions
Insert [ConductorState] into the database.
Insert a DnaDef into the database.
Insert an Entry into the database.
Insert a EntryDef into the database.
Insert a Header into the database.
Insert a [DhtOp] into the database.
Insert a DhtOpLight into the database.
Insert a DhtOpLight into an authored database.
This sets the sql fields so the authored database
can be used in queries with other databases.
Because we are sharing queries across databases
we need the data in the same shape.
Insert a [DhtOp] into the Scratch.
Insert a SignedValidationReceipt into the database.
Insert a [DnaWasm] into the database.
Lock the chain with the given lock id until the given end time.
During this time only the lock id will be unlocked according to is_chain_locked.
The chain can be unlocked for all lock ids at any time by calling unlock_chain.
In theory there can be multiple locks active at once.
If there are multiple locks active at once effectively all locks are locked
because the chain is locked if there are ANY locks that don’t match the
current id being queried.
In practise this is useless so don’t do that. One lock at a time please.
Set the integration dependency of a [DhtOp] in the database.
Set when a [DhtOp] was last publish time
Set the receipt count for a [DhtOp].
Set the whether or not a receipt is required of a [DhtOp] in the database.
Set the validation stage of a [DhtOp] in the database.
Set the validation status of a [DhtOp] in the database.
Set when a [DhtOp] was integrated.
Set withhold publish for a [DhtOp].
Unlock the chain by dropping all records in the lock table. This should be done very carefully as it can e.g. invalidate a shared countersigning session that is inflight.
Unset withhold publish for a [DhtOp].