Telecom & Mnesia - Call Detail Record Collection

[Ulf Wiger]

On Thu, 11 Apr 2002, Per Bergqvist wrote:

>I have a similiar problem like your CDR problem and for this
>purpose I use Berkeley db which is performing well even with
>very large databases.
>
>This however, does not give you a distributed database.  My
>intention is to combine Berkeley db with mnesia transaction
>management, but this is really just an idea at this stage due to
>lack of time.
>
>/Per

I've also thought about similar things. One thing I did in the
past was to add triggers (abort/commit) to the rdbms contrib.
It's not a completely clean solution, but one could perhaps build
on the rdbms framework in order to tie an external database to
mnesia's transaction handling. At least, it doesn't require
hacking mnesia to get it working reasonably well... I think.
(The triggers work well. We use exactly the same solution in AXD
301, and they work even for nested transactions.)

A seemless integration of external tables in mnesia requires some
hacking -- not a lethal dose, but enough to warrant some
consideration first. It's been discussed. Dan G. usually doesn't
do cartwheels when it's brought up, but the idea hasn't been
killed yet. ;)

I have not updated the rdbms contrib for OTP R8 (it still
requires a patch to mnesia_schema, but I've been promised that
my changes will be part of the next mnesia release.) If anyone
actually uses rdbms today, I'm not aware of it.

My next rdbms project was going to be to incorporate support for
fragmented tables, together with a facility to explicitly control
the distribution of objects between fragments. If anyone is
interested in that, let me know, and I might give it slightly
higher priority...

/Uffe