Hmm, this could be exactly what I've wanted. <div><br></div><div>Are there plans to support match?</div><div><br></div><div>And would this be something like I'd have LevelDB running on A and the Erlang drivers communicate over whatever LevelDB protocol there is from B? As in, would it be more like using an external DB than Mnesia. This actually is something I would like since I want to use an Erlang term storage but I want to be able to use services like Dotcloud that separate out database and web services.</div>
<div><br></div><div>Thanks!</div><div>Tristan<br><br><div class="gmail_quote">On Tue, Nov 1, 2011 at 11:44 AM, Joseph Wayne Norton <span dir="ltr"><<a href="mailto:norton@lovely.email.ne.jp">norton@lovely.email.ne.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
LETS is an alternative Erlang Term Storage using LevelDB as the storage implementation. LETS tries to address some bad properties of ETS and DETS. ETS is limited by physical memory. DETS is limited by a 2 GB file size limitation and does not implement ordered sets. LETS has neither of these limitations.<br>
<br>
For testing and comparison purposes, LETS supports three implementations:<br>
• drv C++ Driver with LevelDB backend (default)<br>
• nif C++ NIF with LevelDB backend<br>
• ets Erlang ETS backend<br>
<br>
LETS is not intended to be an exact clone of ETS. The currently supported APIs are:<br>
• new/2<br>
• destroy/2 only driver and nif implementations<br>
• repair/2 only driver and nif implementations<br>
• insert/2<br>
• insert_new/2 only the ets implementation<br>
• delete/1<br>
• delete/2<br>
• delete_all_objects/1 only the ets implementation<br>
• lookup/2<br>
• first/1<br>
• next/2<br>
• info/2 only a subset of items<br>
• tab2list/1<br>
<br>
For further information and instructions to download, please see the <a href="https://github.com/norton/lets" target="_blank">https://github.com/norton/lets</a> repository on GitHub.<br>
<br>
thanks,<br>
<br>
Joe N.<br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div><br></div>