Mnesia Secondary Indexes
Tue Jul 21 21:14:15 CEST 2009
When adding an index to a table field, it appears to me (without
looking at the source), that the indexing method is hash based. While
this is optimal for fast secondary key lookups and join operations, it
does not speed up range based queries. After going through all
available manuals, I'm quite certain it's not possible to use tree-
based indexing on a field, but please correct me if I'm wrong.
My question finally, are there an plans to add tree-based indexing to
mnesia? And in the meantime, are there any existing projects which
hack on this support?
More information about the erlang-questions