forked from lthn/blockchain
fixed storage bug over assets container
This commit is contained in:
parent
37f96db8d5
commit
8e0cf0f142
2 changed files with 6 additions and 0 deletions
|
|
@ -291,6 +291,10 @@ namespace tools
|
|||
|
||||
if (res == MDB_NOTFOUND)
|
||||
return false;
|
||||
if (res != MDB_SUCCESS)
|
||||
{
|
||||
return false;
|
||||
}
|
||||
|
||||
CHECK_AND_ASSERT_MESS_LMDB_DB(res, false, "Unable to mdb_get, h: " << h << ", ks: " << ks);
|
||||
res_buff.assign((const char*)data.mv_data, data.mv_size);
|
||||
|
|
|
|||
|
|
@ -281,6 +281,8 @@ bool blockchain_storage::init(const std::string& config_folder, const boost::pro
|
|||
CHECK_AND_ASSERT_MES(res, false, "Unable to init db container");
|
||||
res = m_db_aliases.init(BLOCKCHAIN_STORAGE_CONTAINER_ALIASES);
|
||||
CHECK_AND_ASSERT_MES(res, false, "Unable to init db container");
|
||||
res = m_db_assets.init(BLOCKCHAIN_STORAGE_CONTAINER_ASSETS);
|
||||
CHECK_AND_ASSERT_MES(res, false, "Unable to init db container");
|
||||
res = m_db_addr_to_alias.init(BLOCKCHAIN_STORAGE_CONTAINER_ADDR_TO_ALIAS);
|
||||
CHECK_AND_ASSERT_MES(res, false, "Unable to init db container");
|
||||
res = m_db_per_block_gindex_incs.init(BLOCKCHAIN_STORAGE_CONTAINER_GINDEX_INCS);
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue