aboutsummaryrefslogtreecommitdiff
path: root/src/crypto
diff options
context:
space:
mode:
authormoneromooo-monero <moneromooo-monero@users.noreply.github.com>2015-12-05 12:40:01 +0000
committermoneromooo-monero <moneromooo-monero@users.noreply.github.com>2015-12-05 12:40:01 +0000
commita70211842693f00f81c2374b7999eda9e184efce (patch)
tree5234e17bb4b478a09db7633d3ef3ad4bf560af8d /src/crypto
parentdb_bdb: read 32 bit heights from keys (diff)
downloadmonero-a70211842693f00f81c2374b7999eda9e184efce.tar.xz
blockchain_dump: fix output key dump for BDB 1-based indices
Berkeley DB uses 1 based indices for RECNO databases, and the implementation of BlockchainDB for Berkeley DB assumes 1 based indices are passed to the API, whereas the LMDB one assumes 0 based indices. This is all internally consisteny, but since the BDB code stores 1 based indices in the database, external users have to be aware of this, as the indices will be off by one depending on which DB is used.
Diffstat (limited to 'src/crypto')
0 files changed, 0 insertions, 0 deletions