diff options
| author | dgrogan@chromium.org <dgrogan@chromium.org@62dab493-f737-651d-591e-8d6aee1b9529> | 2011-04-19 23:01:25 +0000 |
|---|---|---|
| committer | dgrogan@chromium.org <dgrogan@chromium.org@62dab493-f737-651d-591e-8d6aee1b9529> | 2011-04-19 23:01:25 +0000 |
| commit | b743906eeabc925f3e824d91a9747012bf249e2f (patch) | |
| tree | e7cb4f854196c43045756469627920e4e7b146c1 /TODO | |
| parent | b409afe968b6917574ec08e02c4bf6e6f722e3ca (diff) | |
| download | leveldb-b743906eeabc925f3e824d91a9747012bf249e2f.tar.gz | |
Revision created by MOE tool push_codebase.
MOE_MIGRATION=
git-svn-id: https://leveldb.googlecode.com/svn/trunk@22 62dab493-f737-651d-591e-8d6aee1b9529
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 14 |
1 files changed, 0 insertions, 14 deletions
@@ -1,14 +0,0 @@ -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 |