So far we were returning an error, which appears to be a little too
strict, so we now just ignore when a key or value is too large, log it,
and go on.
Fixes#849
Change-Id: Iadd4eaab7459643e22ab3043d1f45e3eab662b30
Let double-delete test pass.
Make leveldb and memdb Deletes go on for ErrNotFound.
Add test for batch deleting nonexisting key, and partial batch delete
errors - fix it for mongo.
Fixes#760.
Change-Id: I0a0e28836a723d245564f3dabaf328bf73bf463a
Use github.com/syndtr/goleveldb/leveldb/memdb in pkg/sorted memKey.
This was the last usage of code.googe.com/p/leveldb-go.
Hopefully tackles issue #600.
Change-Id: Iadcf7b69557cf4834cb2a4353ed0d2159379f423
Previously pkg/jsonconfig and pkg/errorutil
Copied from go4.org at rev d1b8a2fb2de6160036e4801aa5e4d855571078b8
Change-Id: I673ed55b0825baa2607289b6082f205100261d7a
The new package sorted/kvtest provides a generic KeyValue test for all
implementations. Memory, SQLite, and kvfile now use it.
This speeds up the index slurping start-up of my personal Camlistore
server from 30 seconds (when it was doing 17,000+ queries in small
windows) to now just 5 seconds. That 5 seconds can be improved yet
further.
Change-Id: Idd55ba9ccd3ed12a26868a41db1af676aff7b67b
Goal is to iterate faster (notably: for slurping the index to the in-memory
corpus on start-up), by doing fewer copies and generating less garbage.
Change-Id: I054b0de2b994eb1f2356aa8587a466bafeb6cf82
mpl