diff options
| author | Sfan5 <sfan5@live.de> | 2013-09-09 22:46:18 +0200 |
|---|---|---|
| committer | Sfan5 <sfan5@live.de> | 2013-09-09 22:50:51 +0200 |
| commit | 3725179736e2b5372664163470e7ef3dc76529a4 (patch) | |
| tree | 7a56c929ae75530679b3d2f7c9c02fb361760219 /src/leveldb/TODO | |
| parent | 1f3402e7a1e160c4be25c596f33d916b988075fb (diff) | |
| download | minetest-3725179736e2b5372664163470e7ef3dc76529a4.tar.gz minetest-3725179736e2b5372664163470e7ef3dc76529a4.tar.bz2 minetest-3725179736e2b5372664163470e7ef3dc76529a4.zip | |
Use system-wide LevelDB instead of bundled one
Diffstat (limited to 'src/leveldb/TODO')
| -rw-r--r-- | src/leveldb/TODO | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/src/leveldb/TODO b/src/leveldb/TODO deleted file mode 100644 index e603c0713..000000000 --- a/src/leveldb/TODO +++ /dev/null @@ -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. -- 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? |