2023-08-07 17:45:23 +00:00
|
|
|
# nimbus-eth1
|
2023-11-08 16:52:25 +00:00
|
|
|
# Copyright (c) 2023 Status Research & Development GmbH
|
2023-08-07 17:45:23 +00:00
|
|
|
# Licensed under either of
|
|
|
|
# * Apache License, version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or
|
|
|
|
# http://www.apache.org/licenses/LICENSE-2.0)
|
|
|
|
# * MIT license ([LICENSE-MIT](LICENSE-MIT) or
|
|
|
|
# http://opensource.org/licenses/MIT)
|
|
|
|
# at your option. This file may not be copied, modified, or distributed
|
|
|
|
# except according to those terms.
|
|
|
|
|
|
|
|
## Aristo DB -- Transaction interface
|
|
|
|
## ==================================
|
|
|
|
##
|
|
|
|
{.push raises: [].}
|
|
|
|
|
|
|
|
import
|
|
|
|
results,
|
2023-08-17 13:42:01 +00:00
|
|
|
"."/[aristo_desc, aristo_filter, aristo_get, aristo_hashify]
|
2023-08-07 17:45:23 +00:00
|
|
|
|
2023-08-11 17:23:57 +00:00
|
|
|
func isTop*(tx: AristoTxRef): bool
|
2023-09-15 15:23:53 +00:00
|
|
|
func level*(db: AristoDbRef): int
|
2023-08-07 17:45:23 +00:00
|
|
|
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
# Private helpers
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
|
2023-09-15 15:23:53 +00:00
|
|
|
func fromVae(err: (VertexID,AristoError)): AristoError =
|
|
|
|
## Map error pair to error reason component
|
|
|
|
err[1]
|
2023-09-11 20:38:49 +00:00
|
|
|
|
2023-08-11 17:23:57 +00:00
|
|
|
func getDbDescFromTopTx(tx: AristoTxRef): Result[AristoDbRef,AristoError] =
|
|
|
|
if not tx.isTop():
|
|
|
|
return err(TxNotTopTx)
|
|
|
|
let db = tx.db
|
|
|
|
if tx.level != db.stack.len:
|
2023-09-15 15:23:53 +00:00
|
|
|
return err(TxStackGarbled)
|
2023-08-11 17:23:57 +00:00
|
|
|
ok db
|
2023-08-07 17:45:23 +00:00
|
|
|
|
|
|
|
proc getTxUid(db: AristoDbRef): uint =
|
2023-08-11 17:23:57 +00:00
|
|
|
if db.txUidGen == high(uint):
|
|
|
|
db.txUidGen = 0
|
2023-08-07 17:45:23 +00:00
|
|
|
db.txUidGen.inc
|
|
|
|
db.txUidGen
|
|
|
|
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
# Public functions, getters
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
|
2023-08-11 17:23:57 +00:00
|
|
|
func txTop*(db: AristoDbRef): Result[AristoTxRef,AristoError] =
|
2023-08-07 17:45:23 +00:00
|
|
|
## Getter, returns top level transaction if there is any.
|
|
|
|
if db.txRef.isNil:
|
|
|
|
err(TxNoPendingTx)
|
|
|
|
else:
|
|
|
|
ok(db.txRef)
|
|
|
|
|
2023-08-11 17:23:57 +00:00
|
|
|
func isTop*(tx: AristoTxRef): bool =
|
2023-08-07 17:45:23 +00:00
|
|
|
## Getter, returns `true` if the argument `tx` referes to the current top
|
|
|
|
## level transaction.
|
|
|
|
tx.db.txRef == tx and tx.db.top.txUid == tx.txUid
|
|
|
|
|
2023-08-11 17:23:57 +00:00
|
|
|
func level*(tx: AristoTxRef): int =
|
|
|
|
## Getter, positive nesting level of transaction argument `tx`
|
|
|
|
tx.level
|
|
|
|
|
|
|
|
func level*(db: AristoDbRef): int =
|
|
|
|
## Getter, non-negative nesting level (i.e. number of pending transactions)
|
|
|
|
if not db.txRef.isNil:
|
|
|
|
result = db.txRef.level
|
2023-08-07 17:45:23 +00:00
|
|
|
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
# Public functions
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
|
2023-08-11 17:23:57 +00:00
|
|
|
func to*(tx: AristoTxRef; T: type[AristoDbRef]): T =
|
|
|
|
## Getter, retrieves the parent database descriptor from argument `tx`
|
2023-08-07 17:45:23 +00:00
|
|
|
tx.db
|
|
|
|
|
2023-09-18 20:20:28 +00:00
|
|
|
proc forkTx*(
|
|
|
|
tx: AristoTxRef; # Transaction descriptor
|
|
|
|
dontHashify = false; # Process/fix MPT hashes
|
|
|
|
): Result[AristoDbRef,AristoError] =
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
## Clone a transaction into a new DB descriptor accessing the same backend
|
|
|
|
## database (if any) as the argument `db`. The new descriptor is linked to
|
2023-09-11 20:38:49 +00:00
|
|
|
## the transaction parent and is fully functional as a forked instance (see
|
|
|
|
## comments on `aristo_desc.reCentre()` for details.)
|
2023-08-17 13:42:01 +00:00
|
|
|
##
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
## Input situation:
|
|
|
|
## ::
|
|
|
|
## tx -> db0 with tx is top transaction, tx.level > 0
|
|
|
|
##
|
|
|
|
## Output situation:
|
|
|
|
## ::
|
|
|
|
## tx -> db0 \
|
|
|
|
## > share the same backend
|
|
|
|
## tx1 -> db1 /
|
|
|
|
##
|
|
|
|
## where `tx.level > 0`, `db1.level == 1` and `db1` is returned. The
|
|
|
|
## transaction `tx1` can be retrieved via `db1.txTop()`.
|
|
|
|
##
|
2023-09-11 20:38:49 +00:00
|
|
|
## The new DB descriptor will contain a copy of the argument transaction
|
|
|
|
## `tx` as top layer of level 1 (i.e. this is he only transaction.) Rolling
|
|
|
|
## back will end up at the backend layer (incl. backend filter.)
|
2023-08-17 13:42:01 +00:00
|
|
|
##
|
2023-09-18 20:20:28 +00:00
|
|
|
## If the arguent flag `dontHashify` is passed `true`, the clone descriptor
|
|
|
|
## will *NOT* be hashified right after construction.
|
|
|
|
##
|
2023-09-11 20:38:49 +00:00
|
|
|
## Use `aristo_desc.forget()` to clean up this descriptor.
|
2023-08-17 13:42:01 +00:00
|
|
|
##
|
|
|
|
let db = tx.db
|
|
|
|
|
|
|
|
# Provide new top layer
|
2023-08-18 19:46:55 +00:00
|
|
|
var topLayer: LayerRef
|
2023-08-17 13:42:01 +00:00
|
|
|
if db.txRef == tx:
|
|
|
|
topLayer = db.top.dup
|
|
|
|
elif tx.level < db.stack.len:
|
|
|
|
topLayer = db.stack[tx.level].dup
|
|
|
|
else:
|
|
|
|
return err(TxArgStaleTx)
|
|
|
|
if topLayer.txUid != tx.txUid:
|
|
|
|
return err(TxArgStaleTx)
|
|
|
|
topLayer.txUid = 1
|
|
|
|
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
# Provide new empty stack layer
|
2023-08-17 13:42:01 +00:00
|
|
|
let stackLayer = block:
|
|
|
|
let rc = db.getIdgBE()
|
|
|
|
if rc.isOk:
|
2023-08-18 19:46:55 +00:00
|
|
|
LayerRef(vGen: rc.value)
|
2023-08-17 13:42:01 +00:00
|
|
|
elif rc.error == GetIdgNotFound:
|
2023-08-18 19:46:55 +00:00
|
|
|
LayerRef()
|
2023-08-17 13:42:01 +00:00
|
|
|
else:
|
|
|
|
return err(rc.error)
|
|
|
|
|
2023-09-11 20:38:49 +00:00
|
|
|
let txClone = ? db.fork(rawToplayer = true)
|
|
|
|
|
2023-08-17 13:42:01 +00:00
|
|
|
# Set up clone associated to `db`
|
2023-09-11 20:38:49 +00:00
|
|
|
txClone.top = topLayer # is a deep copy
|
|
|
|
txClone.stack = @[stackLayer]
|
|
|
|
txClone.roFilter = db.roFilter # no need to copy contents (done when updated)
|
|
|
|
txClone.backend = db.backend
|
|
|
|
txClone.txUidGen = 1
|
2023-08-17 13:42:01 +00:00
|
|
|
|
|
|
|
# Install transaction similar to `tx` on clone
|
|
|
|
txClone.txRef = AristoTxRef(
|
|
|
|
db: txClone,
|
|
|
|
txUid: 1,
|
|
|
|
level: 1)
|
|
|
|
|
2023-09-18 20:20:28 +00:00
|
|
|
if db.top.dirty and not dontHashify:
|
|
|
|
let rc = txClone.hashify()
|
|
|
|
if rc.isErr:
|
|
|
|
discard txClone.forget()
|
|
|
|
return err(rc.error.fromVae)
|
|
|
|
|
2023-08-17 13:42:01 +00:00
|
|
|
ok(txClone)
|
|
|
|
|
2023-09-18 20:20:28 +00:00
|
|
|
|
|
|
|
proc forkTop*(
|
|
|
|
db: AristoDbRef;
|
|
|
|
dontHashify = false; # Process/fix MPT hashes
|
|
|
|
): Result[AristoDbRef,AristoError] =
|
2023-09-11 20:38:49 +00:00
|
|
|
## Variant of `forkTx()` for the top transaction if there is any. Otherwise
|
|
|
|
## the top layer is cloned, only.
|
2023-08-17 13:42:01 +00:00
|
|
|
##
|
2023-09-11 20:38:49 +00:00
|
|
|
## Use `aristo_desc.forget()` to clean up this descriptor.
|
2023-08-17 13:42:01 +00:00
|
|
|
##
|
|
|
|
if db.txRef.isNil:
|
2023-09-11 20:38:49 +00:00
|
|
|
let dbClone = ? db.fork(rawToplayer = true)
|
|
|
|
|
|
|
|
dbClone.top = db.top.dup # is a deep copy
|
|
|
|
dbClone.roFilter = db.roFilter # no need to copy contents when updated
|
|
|
|
dbClone.backend = db.backend
|
2023-08-17 13:42:01 +00:00
|
|
|
|
2023-09-18 20:20:28 +00:00
|
|
|
if db.top.dirty and not dontHashify:
|
|
|
|
let rc = dbClone.hashify()
|
|
|
|
if rc.isErr:
|
|
|
|
discard dbClone.forget()
|
|
|
|
return err(rc.error.fromVae)
|
2023-08-17 13:42:01 +00:00
|
|
|
return ok(dbClone)
|
|
|
|
|
2023-09-18 20:20:28 +00:00
|
|
|
db.txRef.forkTx dontHashify
|
2023-08-17 13:42:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
proc exec*(
|
|
|
|
tx: AristoTxRef;
|
|
|
|
action: AristoDbAction;
|
2023-09-18 20:20:28 +00:00
|
|
|
dontHashify = false; # Process/fix MPT hashes
|
2023-09-26 09:21:13 +00:00
|
|
|
): Result[void,AristoError] =
|
2023-09-18 20:20:28 +00:00
|
|
|
## Execute function argument `action()` on a temporary `tx.forkTx()`
|
|
|
|
## transaction clone database. After return, the temporary database gets
|
2023-08-17 13:42:01 +00:00
|
|
|
## destroyed.
|
|
|
|
##
|
2023-09-18 20:20:28 +00:00
|
|
|
## If the arguent flag `dontHashify` is passed `true`, the clone database
|
|
|
|
## will *NOT* be hashified right after construction.
|
|
|
|
##
|
|
|
|
let db = ? tx.forkTx dontHashify
|
2023-08-17 13:42:01 +00:00
|
|
|
db.action()
|
2023-09-11 20:38:49 +00:00
|
|
|
? db.forget()
|
2023-08-07 17:45:23 +00:00
|
|
|
ok()
|
|
|
|
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
# Public functions: Transaction frame
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
|
2023-09-15 15:23:53 +00:00
|
|
|
proc txBegin*(db: AristoDbRef): Result[AristoTxRef,AristoError] =
|
2023-08-07 17:45:23 +00:00
|
|
|
## Starts a new transaction.
|
|
|
|
##
|
|
|
|
## Example:
|
|
|
|
## ::
|
|
|
|
## proc doSomething(db: AristoDbRef) =
|
|
|
|
## let tx = db.begin
|
|
|
|
## defer: tx.rollback()
|
|
|
|
## ... continue using db ...
|
|
|
|
## tx.commit()
|
|
|
|
##
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
if db.level != db.stack.len:
|
|
|
|
return err(TxStackGarbled)
|
2023-08-11 17:23:57 +00:00
|
|
|
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
db.stack.add db.top.dup # push (save and use top later)
|
|
|
|
db.top.txUid = db.getTxUid()
|
2023-08-07 17:45:23 +00:00
|
|
|
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
db.txRef = AristoTxRef(
|
|
|
|
db: db,
|
|
|
|
txUid: db.top.txUid,
|
|
|
|
parent: db.txRef,
|
|
|
|
level: db.stack.len)
|
2023-08-11 17:23:57 +00:00
|
|
|
|
|
|
|
ok db.txRef
|
2023-08-07 17:45:23 +00:00
|
|
|
|
2023-09-15 15:23:53 +00:00
|
|
|
|
2023-08-11 17:23:57 +00:00
|
|
|
proc rollback*(
|
|
|
|
tx: AristoTxRef; # Top transaction on database
|
2023-09-15 15:23:53 +00:00
|
|
|
): Result[void,AristoError] =
|
2023-08-07 17:45:23 +00:00
|
|
|
## Given a *top level* handle, this function discards all database operations
|
|
|
|
## performed for this transactio. The previous transaction is returned if
|
|
|
|
## there was any.
|
|
|
|
##
|
2023-09-15 15:23:53 +00:00
|
|
|
let db = ? tx.getDbDescFromTopTx()
|
2023-08-07 17:45:23 +00:00
|
|
|
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
# Roll back to previous layer.
|
|
|
|
db.top = db.stack[^1]
|
|
|
|
db.stack.setLen(db.stack.len-1)
|
2023-08-07 17:45:23 +00:00
|
|
|
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
db.txRef = db.txRef.parent
|
|
|
|
ok()
|
2023-08-07 17:45:23 +00:00
|
|
|
|
2023-08-11 17:23:57 +00:00
|
|
|
|
|
|
|
proc commit*(
|
|
|
|
tx: AristoTxRef; # Top transaction on database
|
|
|
|
dontHashify = false; # Process/fix MPT hashes
|
2023-09-15 15:23:53 +00:00
|
|
|
): Result[void,AristoError] =
|
2023-08-07 17:45:23 +00:00
|
|
|
## Given a *top level* handle, this function accepts all database operations
|
|
|
|
## performed through this handle and merges it to the previous layer. The
|
|
|
|
## previous transaction is returned if there was any.
|
|
|
|
##
|
2023-08-11 17:23:57 +00:00
|
|
|
## Unless the argument `dontHashify` is set `true`, the function will process
|
|
|
|
## Merkle Patricia Treee hashes unless there was no change to this layer.
|
|
|
|
## This may produce additional errors (see `hashify()`.)
|
2023-09-15 15:23:53 +00:00
|
|
|
##
|
|
|
|
let db = ? tx.getDbDescFromTopTx()
|
2023-08-07 17:45:23 +00:00
|
|
|
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
if db.top.dirty and not dontHashify:
|
|
|
|
discard ? db.hashify().mapErr fromVae
|
|
|
|
|
|
|
|
# Keep top and discard layer below
|
|
|
|
db.top.txUid = db.stack[^1].txUid
|
|
|
|
db.stack.setLen(db.stack.len-1)
|
2023-08-07 17:45:23 +00:00
|
|
|
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
db.txRef = db.txRef.parent
|
|
|
|
ok()
|
2023-08-07 17:45:23 +00:00
|
|
|
|
|
|
|
|
|
|
|
proc collapse*(
|
2023-08-11 17:23:57 +00:00
|
|
|
tx: AristoTxRef; # Top transaction on database
|
|
|
|
commit: bool; # Commit if `true`, otherwise roll back
|
|
|
|
dontHashify = false; # Process/fix MPT hashes
|
2023-09-15 15:23:53 +00:00
|
|
|
): Result[void,AristoError] =
|
2023-08-07 17:45:23 +00:00
|
|
|
## Iterated application of `commit()` or `rollback()` performing the
|
|
|
|
## something similar to
|
|
|
|
## ::
|
2023-08-11 17:23:57 +00:00
|
|
|
## while true:
|
|
|
|
## discard tx.commit() # ditto for rollback()
|
|
|
|
## if db.topTx.isErr: break
|
|
|
|
## tx = db.topTx.value
|
2023-08-07 17:45:23 +00:00
|
|
|
##
|
2023-09-15 15:23:53 +00:00
|
|
|
## The `dontHashify` flag is treated as described for `commit()`
|
|
|
|
##
|
|
|
|
let db = ? tx.getDbDescFromTopTx()
|
|
|
|
|
|
|
|
if commit:
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
# For commit, hashify the current layer if requested and install it
|
|
|
|
if db.top.dirty and not dontHashify:
|
|
|
|
discard ? db.hashify().mapErr fromVae
|
2023-09-15 15:23:53 +00:00
|
|
|
else:
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
# For rollback hashify the stack bottom layer if requested and install it
|
|
|
|
if db.top.dirty and not dontHashify:
|
|
|
|
db.stack[0].swap db.top
|
|
|
|
|
|
|
|
var restore = true
|
|
|
|
defer:
|
|
|
|
if restore: db.stack[0].swap db.top
|
|
|
|
discard ? db.hashify().mapErr fromVae
|
|
|
|
restore = false
|
|
|
|
|
|
|
|
db.top.txUid = 0
|
|
|
|
db.stack.setLen(0)
|
|
|
|
db.txRef = AristoTxRef(nil)
|
|
|
|
ok()
|
2023-08-07 17:45:23 +00:00
|
|
|
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
# Public functions: save database
|
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
|
2023-08-10 20:01:28 +00:00
|
|
|
proc stow*(
|
2023-08-11 17:23:57 +00:00
|
|
|
db: AristoDbRef; # Database
|
|
|
|
persistent = false; # Stage only unless `true`
|
|
|
|
dontHashify = false; # Process/fix MPT hashes
|
|
|
|
chunkedMpt = false; # Partial data (e.g. from `snap`)
|
2023-09-15 15:23:53 +00:00
|
|
|
): Result[void,AristoError] =
|
2023-08-11 17:23:57 +00:00
|
|
|
## If there is no backend while the `persistent` argument is set `true`,
|
2023-09-12 18:45:12 +00:00
|
|
|
## the function returns immediately with an error. The same happens if there
|
2023-08-17 13:42:01 +00:00
|
|
|
## is a pending transaction.
|
2023-08-11 17:23:57 +00:00
|
|
|
##
|
|
|
|
## The `dontHashify` is treated as described for `commit()`.
|
2023-08-10 20:01:28 +00:00
|
|
|
##
|
2023-08-11 17:23:57 +00:00
|
|
|
## The function then merges the data from the top layer cache into the
|
2023-08-10 20:01:28 +00:00
|
|
|
## backend stage area. After that, the top layer cache is cleared.
|
|
|
|
##
|
2023-08-11 17:23:57 +00:00
|
|
|
## Staging the top layer cache might fail withh a partial MPT when it is
|
|
|
|
## set up from partial MPT chunks as it happens with `snap` sync processing.
|
|
|
|
## In this case, the `chunkedMpt` argument must be set `true` (see alse
|
|
|
|
## `fwdFilter`.)
|
|
|
|
##
|
|
|
|
## If the argument `persistent` is set `true`, all the staged data are merged
|
|
|
|
## into the physical backend database and the staged data area is cleared.
|
2023-08-10 20:01:28 +00:00
|
|
|
##
|
2023-08-17 13:42:01 +00:00
|
|
|
if not db.txRef.isNil:
|
2023-09-15 15:23:53 +00:00
|
|
|
return err(TxPendingTx)
|
2023-08-17 13:42:01 +00:00
|
|
|
if 0 < db.stack.len:
|
2023-09-15 15:23:53 +00:00
|
|
|
return err(TxStackGarbled)
|
2023-09-11 20:38:49 +00:00
|
|
|
if persistent and not db.canResolveBackendFilter():
|
2023-09-15 15:23:53 +00:00
|
|
|
return err(TxBackendNotWritable)
|
2023-08-17 13:42:01 +00:00
|
|
|
|
|
|
|
if db.top.dirty and not dontHashify:
|
2023-09-15 15:23:53 +00:00
|
|
|
discard ? db.hashify().mapErr fromVae
|
2023-08-10 20:01:28 +00:00
|
|
|
|
2023-09-15 15:23:53 +00:00
|
|
|
let fwd = ? db.fwdFilter(db.top, chunkedMpt).mapErr fromVae
|
2023-08-10 20:01:28 +00:00
|
|
|
|
2023-08-18 19:46:55 +00:00
|
|
|
if fwd.isValid:
|
|
|
|
# Merge `top` layer into `roFilter`
|
2023-09-15 15:23:53 +00:00
|
|
|
? db.merge(fwd).mapErr fromVae
|
2023-08-18 19:46:55 +00:00
|
|
|
db.top = LayerRef(vGen: db.roFilter.vGen)
|
2023-08-17 13:42:01 +00:00
|
|
|
|
|
|
|
if persistent:
|
2023-09-15 15:23:53 +00:00
|
|
|
? db.resolveBackendFilter()
|
2023-08-18 19:46:55 +00:00
|
|
|
db.roFilter = FilterRef(nil)
|
2023-08-10 20:01:28 +00:00
|
|
|
|
|
|
|
# Delete or clear stack and clear top
|
|
|
|
db.stack.setLen(0)
|
2023-08-18 19:46:55 +00:00
|
|
|
db.top = LayerRef(vGen: db.top.vGen, txUid: db.top.txUid)
|
2023-08-07 17:45:23 +00:00
|
|
|
|
|
|
|
ok()
|
|
|
|
|
2023-08-10 20:01:28 +00:00
|
|
|
proc stow*(
|
2023-08-11 17:23:57 +00:00
|
|
|
db: AristoDbRef; # Database
|
|
|
|
stageLimit: int; # Policy based persistent storage
|
|
|
|
dontHashify = false; # Process/fix MPT hashes
|
|
|
|
chunkedMpt = false; # Partial data (e.g. from `snap`)
|
2023-09-15 15:23:53 +00:00
|
|
|
): Result[void,AristoError] =
|
2023-08-11 17:23:57 +00:00
|
|
|
## Variant of `stow()` with the `persistent` argument replaced by
|
|
|
|
## `stageLimit < max(db.roFilter.bulk, db.top.bulk)`.
|
|
|
|
db.stow(
|
|
|
|
persistent = (stageLimit < max(db.roFilter.bulk, db.top.bulk)),
|
|
|
|
dontHashify = dontHashify,
|
|
|
|
chunkedMpt = chunkedMpt)
|
2023-08-10 20:01:28 +00:00
|
|
|
|
2023-08-07 17:45:23 +00:00
|
|
|
# ------------------------------------------------------------------------------
|
|
|
|
# End
|
|
|
|
# ------------------------------------------------------------------------------
|