diff options
| author | dgrogan@chromium.org <dgrogan@chromium.org@62dab493-f737-651d-591e-8d6aee1b9529> | 2011-04-19 23:11:15 +0000 |
|---|---|---|
| committer | dgrogan@chromium.org <dgrogan@chromium.org@62dab493-f737-651d-591e-8d6aee1b9529> | 2011-04-19 23:11:15 +0000 |
| commit | 69c6d38342a1fab5f7f2921aa2e9c0e60ba90e35 (patch) | |
| tree | bea96813c653d9e32277cb86cb517ddd90d0595c /TODO | |
| parent | b743906eeabc925f3e824d91a9747012bf249e2f (diff) | |
| download | leveldb-69c6d38342a1fab5f7f2921aa2e9c0e60ba90e35.tar.gz | |
reverting disastrous MOE commit, returning to r21
git-svn-id: https://leveldb.googlecode.com/svn/trunk@23 62dab493-f737-651d-591e-8d6aee1b9529
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -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. + +api changes? +- Efficient large value reading and writing + +Faster Get implementation |