Import LevelDB 1.5, it will be used for the transaction database.

2012-06-25 11:17:22 +02:00
parent 38ac953b9d
commit 5e650d6d2d
130 changed files with 25488 additions and 4 deletions
--- a/src/leveldb/TODO
+++ b/src/leveldb/TODO
@@ -0,0 +1,13 @@
+ss
+- Stats
+
+db
+- Maybe implement DB::BulkDeleteForRange(start_key, end_key)
+  that would blow away files whose ranges are entirely contained
+  within [start_key..end_key]?  For Chrome, deletion of obsolete
+  object stores, etc. can be done in the background anyway, so
+  probably not that important.
+
+After a range is completely deleted, what gets rid of the
+corresponding files if we do no future changes to that range.  Make
+the conditions for triggering compactions fire in more situations?