GitLab

Improve Query performance

The verification is not cheap and should not be necessary.  The only way
it could be invalid is if the database is corrupt or someone manually
modified the database outside of the datastore interface.

Fix bug in LevelDB datastore's Delete() method.

License: MIT
Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>

License: MIT
Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>

LevelDB Delete() method will not return ErrNotFound, so check that the
key exists first by calling Has() and return ds.ErrNotFound if Has()
returns false.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>

implement batch ops for different datastore types

rename Transaction to Batch

Revert "add in support for batched writes"

add in benchmarks for put and batchput

move batching into separate interface

address concerns from PR

regrab old code

this is not a good inteface. should fix it

License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>

ThreadsafeDatastore declares a datastore thread-safe by extending the
Datastore interface.

Callers who desire thread-safety may use this interface to assure that
the datastores they use provide this property.

Datastore implementers may satisfy the ThreadsafeDatastore interface
by defining the no-op method `IsThreadSafe()`