[ANN] levigo, a wrapper for LevelDB

[Jeff Hodges]

levigo provides the ability to create and access LevelDB databases
from Go. It can be installed with the go tool from and is maintained
at <https://github.com/jmhodges/levigo>.

The godoc can be found at
<http://gopkgdoc.appspot.com/pkg/github.com/jmhodges/levigo> and is
pretty complete.

Installation requires the LevelDB shared library to be present, and
may require the use of the CGO_CFLAGS and CGO_LDFLAGS environment
variables depending on where you installed the LevelDB library. See
the README <https://github.com/jmhodges/levigo#readme> for details.

[Ugorji Nwoke]

There's also the leveldb-go package which is a leveldb implementation in Go, written and maintained by the Go Core Team.

http://code.google.com/p/leveldb-go/

http://code.google.com/p/snappy-go/

I've been looking into using leveldb-go. Are you familiar with it, and do you have any thoughts on why/whether it's better to depend on the C++ implementation vs the pure Go implementation.

Some things I've thought about are whether enhancements made to the C++ version (which is actively developed, especially since it's a part of chrome) make it back into the Go port.

[Jeff Hodges]

I'm excited by the possibility of leveldb-go, but it's not complete
and does not have the concentrated engineering effort being put into
it as the original LevelDB.

If you follow along on the LevelDB list, you'll see a lot of
engineering movement that's not, currently, happening in leveldb-go.
This wrapper solved my problem (and hopefully yours) now.

(Oh, and while Nigel Tao works on both leveldb-go and golang, it's not
being maintained by the whole golang team.)

[Ugorji Nwoke]

Makes sense. 

Thanks for the package.

On Monday, April 2, 2012 1:04:49 PM UTC-4, Jeff Hodges wrote:

I'm excited by the possibility of leveldb-go, but it's not complete
and does not have the concentrated engineering effort being put into
it as the original LevelDB.

If you follow along on the LevelDB list, you'll see a lot of
engineering movement that's not, currently, happening in leveldb-go.
This wrapper solved my problem (and hopefully yours) now.

(Oh, and while Nigel Tao works on both leveldb-go and golang, it's not
being maintained by the whole golang team.)

> There's also the leveldb-go package which is a leveldb implementation in Go,