I just released a new version of LimDB, the table-like interface to the LMDB in-process key value store. I've been using it in almost all my projects, mostly small web apps, and it works like a charm. I also found the interface very satisfying to use, so I think I struck the right balance between easy-to-dive-into and keeping the underlying API's power.
This is actually not a bugfix release, because I didn't find any bugs. But this is a glue project, putting a simple friendly face on a very mature and well understood piece of software, and there is really good test coverage, so this is to be expected.
In my web app, I noticed my very minimal set of table-like proc used to access the underlying LMDB database was resulting in a bit too verbose code, so I added all the procs from std/tables that made sense to me. Those are: getOrDefault, hasKeyOrPut, getOrPut, pop and take, and I added a new getOrPut. So this ought be a more useful auto-persisting table now.
I hope this is useful to you! Give it a whirl and let me know what you think, if you haven't already.
Thanks for this great library!
Incredible easy to use :)
Thanks! That was a main design goal, glad it worked.
I'd been using nim-lmdb before in my web apps, which already worked great, but I wanted something a little less verbose.