ARCHIVE/clio
1
0
Fork 0
mirror of https://github.com/XRPLF/clio.git synced 2025-12-05 16:58:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
CJ Cobb
2021-06-23 13:28:28 -04:00
committed by GitHub
parent efa0dd5478
commit 25ca6590d1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/backend/README.md
View File

@@ -8,7 +8,7 @@ The data model used by clio is called the flat map data model. The flat map data
SHAMap inner nodes, and instead only stores the raw ledger objects contained in the leaf node. Ledger objects SHAMap inner nodes, and instead only stores the raw ledger objects contained in the leaf node. Ledger objects
are stored in the database with a compound key of `(object_id, ledger_sequence)`, where `ledger_sequence` is the are stored in the database with a compound key of `(object_id, ledger_sequence)`, where `ledger_sequence` is the
ledger in which the object was created or modified. Objects are then fetched using an inequality operation, ledger in which the object was created or modified. Objects are then fetched using an inequality operation,
such as `SELECT * FROM objects WHERE object_id = id AND ledger_sequence <= seq`, where `seq` is the ledger such as `SELECT * FROM objects WHERE object_id = id AND ledger_sequence <= seq order by ledger_sequence limit 1`, where `seq` is the ledger
in which we are trying to look up the object. When an object is deleted, we write an empty blob. in which we are trying to look up the object. When an object is deleted, we write an empty blob.
Transactions are stored in a separate table, where the key is the hash. Transactions are stored in a separate table, where the key is the hash.