{"push_id":617205464,"size":2,"distinct_size":2,"ref":"refs/heads/ramdb","head":"d56b7d388818efe4187dd365660aa4a59c03986e","before":"f1a2629219030052677b19f3933aa810d4d3daa9","commits":[{"sha":"091aed6cab162f69324444bb2fb9d841db3184de","author":{"email":"6e69f6465f958995e7067ca6453d1440b4b7abff@gmail.com","name":"Thomas Winget"},"message":"In-memory DB appears to be working, need save/load\n\n- The in-memory DB seems like it's ready to go, but cannot yet save and\nload.  That should be simple, but this feels like a good place to\ncommit.\n\n- Several functions were noted to be unnecessary in BlockchainDB but\nrather necessary for specific implementations, and have thus been\nrelocated accordingly.\n\n- block and transaction simple metadata structs have been moved from\nblockchain{,_storage}.h to cryptonote_basic.h as they're needed by the\nin-memory DB as well and thus should be somewhere common to both.\n\n- Since in-mem uses vectors, insertion and deletion order of blocks,\ntransactions, and output metadata must be inverse of one-another.\nBlockchain has been modified accordingly.  This should not affect LMDB\nor BDB since they use hashed/sequential keys rather than vector\nindices.","distinct":true,"url":"https://api.github.com/repos/tewinget/bitmonero/commits/091aed6cab162f69324444bb2fb9d841db3184de"},{"sha":"d56b7d388818efe4187dd365660aa4a59c03986e","author":{"email":"6e69f6465f958995e7067ca6453d1440b4b7abff@gmail.com","name":"Thomas Winget"},"message":"Save/load work for in-mem BlockchainDB\n\n- Compatible with current upstream in-mem database.","distinct":true,"url":"https://api.github.com/repos/tewinget/bitmonero/commits/d56b7d388818efe4187dd365660aa4a59c03986e"}]}