add singleton like behavior to python wrapper to prevent crash from duplicate instantiations of rangeapi
removing dtor in berkeley_db, as it appears dbstl actually does clean up after itself; and trying to cleanup for it (even with its APIs) bugs it
prefix statsd metric name with "rangexx.", and normalize event logs from Timer
fixed inclusion of dbcxx which interferese with dbstl symbols, and link order causes undefined behavior; cleaned up some db handling
db fixup, beginning full integration testing
update log documentation, change debug5-9 to be log-only (no metrics); change Timer public, but makes its ctor private, and add Emitter as a friend so that it can be added as a member variable (in GraphTxn for example) and copy-constructed (still public) from Emitter::start_timer
fixes for multithreading
fix remove_*_edge functions, refactor to remove duplicate code
fix remove() to add and remove a cyclic edge on a removed node to ensure the change triggers a node version bump
fix unit tests, and add start of formal integration test
increased logging, switch of loglevel to above/below the metrics emit threshold in various places, add thread registration to api and python wrapper