Jordan Hrycaj 9e50af839f Core db+aristo update storage trie handling (#2023) ... * CoreDb: Test module with additional sample selector cmd line options * Aristo: Do not automatically remove a storage trie with the account why: This is an unnecessary side effect. Rather than using an automatism, a a storage root must be deleted manually. * Aristo: Can handle stale storage root vertex IDs as empty IDs. why: This is currently needed for the ledger API supporting both, a legacy and the `Aristo` database backend. This feature can be disabled at compile time by re-setting the `LOOSE_STORAGE_TRIE_COUPLING` flag in the `aristo_constants` module. * CoreDb+Aristo: Flush/delete storage trie when deleting account why: On either backend, a deleted account leave a dangling storage trie on the database. For consistency nn the legacy backend, storage tries must not be deleted as they might be shared by several accounts whereas on `Aristo` they are always unique.		2024-02-12 19:37:00 +00:00
..
api_legacy_desc.nim	Core db update api tracking (#1907)	2023-11-24 22:16:21 +00:00
api_new_desc.nim	Core db+ledger aristo backend update (#2006)	2024-02-02 20:23:04 +00:00
api_tracking.nim	Core db+aristo update storage trie handling (#2023)	2024-02-12 19:37:00 +00:00
base_desc.nim	Core db+aristo update storage trie handling (#2023)	2024-02-12 19:37:00 +00:00
validate.nim	Core db+aristo update storage trie handling (#2023)	2024-02-12 19:37:00 +00:00