GitLab

This way, we can abstract over transactions, datastores, and batches when we
just need to write to the datastore.

We can also add this as an extension but it's simple enough I'd like to add it
directly to the Datastore.

Use-case: The blockstore now has a GetSize and bitswap uses it for packing
multiple blocks into a single message. Unfortunately, this means that bitswap is
now calling blockstore.GetSize which calls datastore.Get which tends to be more
expensive than datastore.Has.

This reverts commit 8cca1683a03aace2013e48679302100b3580d2ca.

None of our actual datastores support any other types and the cast noise gets
really annoying after a while.

This adds a PersistentDatastore interface which allows datastores
to report DiskUsage().

It implementes the interface on all wrapper types, which return
0 if the wrapped datastore does not provide this method.

Related: https://github.com/ipfs/go-ipfs/pull/4550

License: MIT
Signed-off-by: Vasily Kolobkov <polezaivsani@openmailbox.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

https://code.google.com/p/go-wiki/wiki/CodeReviewComments#Named_Result_Parameters

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()`