aboutsummaryrefslogtreecommitdiff
path: root/src/blockchain_db/lmdb (follow)
AgeCommit message (Collapse)AuthorFilesLines
2015-05-16Allow BlockchainLMDB to be opened in read-only modewarptangent1-2/+6
Have blockchain_export use read-only mode when source is BlockchainLMDB.
2015-05-08Update log statementswarptangent1-1/+1
Use filesystem path conversion to string() instead of c_str(). Windows may otherwise output an address.
2015-03-25Steps toward multiple dbs available -- workingThomas Winget2-10/+1
There will need to be some more refactoring for these changes to be considered complete/correct, but for now it's working. new daemon cli argument "--db-type", works for LMDB and BerkeleyDB. A good deal of refactoring is also present in this commit, namely Blockchain no longer instantiates BlockchainDB, but rather is passed a pointer to an already-instantiated BlockchainDB on init().
2015-03-17Pull blockchain changes into berkeleydb branchThomas Winget2-11/+17
2015-03-16Try to not pollute cryptonote namespaceThomas Winget2-47/+47
2015-03-16Add support for database open with flagswarptangent2-3/+2
Add support to: - BlockchainDB, BlockchainLMDB - blockchain_import utility to open LMDB database with one or more LMDB flags. Sample use: $ blockchain_import --database lmdb#nosync $ blockchain_import --database lmdb#nosync,nometasync
2015-03-16Add mdb_flags variable to LMDB database openwarptangent1-1/+2
2015-03-15Update and relocate comment that applies class widewarptangent1-8/+14
2015-03-13BlockchainDB implementations have names nowThomas Winget2-0/+9
In order to make things more general, BlockchainDB now has get_db_name() which should return a string with the "name" of that type of db. This "name" will be the subfolder name that holds that db type's files within the monero folder. Small bugfix: blockchain_converter was not correctly appending this in the prior hard-coded-string implementation of the subfolder data directory concept.
2015-03-06Moved BlockchainDB into its own src/ subfolderThomas Winget2-0/+2122
Ostensibly janitorial work, but should be more relevant later down the line. Things that depend on core cryptonote things (i.e. cryptonote_core) don't necessarily depend on BlockchainDB and thus have no need to have BlockchainDB baked in with them.