Thu May 11 23:28:20 CEST 2017
On Thu, May 11, 2017 at 10:32 PM, Adam Rutkowski <hq@REDACTED> wrote:
> On Tue, May 9, 2017, at 22:00, Vlad Dumitrescu wrote:
> I was thinking of an ets+dets combo, but it may be tricky to get the
> details right. Is there something like this out there? Would it be better
> to just use mnesia?
> Hi Vlad,
> Apologies if this sounds blunt, but isn't mnesia in fact an ETS+DETS combo
> with lots of tricky details?
> With DETS alone I often get the tables corrupted, erlang-history is the
> prime example -- `rm ~/.erlang-hist.nonode@REDACTED` is my weekly
> What other properties are you looking for? Why _not_ mnesia in your case?
No problems. There are of course additional requirements, but the main
issue with mnesia is that I would like to be able to build the data store
from fragments that are precomputed inependently from each other, without
needing to import them or something like that. These fragments can be dets
tables or even simple files (one per entry), with the in-memory table just
keeping references to them and sometimes computing and adding new ones.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions