From 58841ef12f6cba1bb622353c1fcaa0e3c6fb46c9 Mon Sep 17 00:00:00 2001
From: Ilya Zhuravlev <zhuravlevilya@ya.ru>
Date: Tue, 23 Oct 2012 01:18:44 +0400
Subject: Add dummy and LevelDB database backends

---
 src/leveldb/TODO | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 src/leveldb/TODO

(limited to 'src/leveldb/TODO')

diff --git a/src/leveldb/TODO b/src/leveldb/TODO
new file mode 100644
index 000000000..e603c0713
--- /dev/null
+++ b/src/leveldb/TODO
@@ -0,0 +1,14 @@
+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.
+- There have been requests for MultiGet.
+
+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?
-- 
cgit v1.2.3