Supervisor hierarchy question

[Chandrashekhar Mullaparthi]

Valentin,

Our entire customer database is in Mnesia - that's about 18 million records.
And it is used by countless number of services for realtime checks.

cheers
Chandru

> -----Original Message-----
> From: Valentin Micic [mailto:valentin@REDACTED] 
> Sent: 19 January 2005 06:29
> To: Eric Merritt; Torbjorn Tornkvist
> Cc: erlang-questions@REDACTED
> Subject: Re: Supervisor hierarchy question
> 
> 
> Would it be too crazy to atempt to provide a mnesia access 
> module that would
> use mysql or similar database for storage?
> Thus, instead of using ODBC or similar one could use 
> mnesia:activity....
> 
> BTW: I've been asked the other day why did I choose a Disney 
> (a.k.a. Mickey
> Mouse) Database for implementation of some serious data 
> volumes. They said,
> Even Ericsson is not using MNESIA... not that we have any 
> problems, but...
> 
> How does one fight such (IMHO) unjustified argument(s)? Can 
> anybody tell me
> of any comercial application of MNESIA.
> 
> Valentin.
> 
> 
> ----- Original Message -----
> From: "Eric Merritt" <cyberlync@REDACTED>
> To: "Torbjorn Tornkvist" <tobbe@REDACTED>
> Cc: <erlang-questions@REDACTED>
> Sent: Wednesday, January 19, 2005 12:25 AM
> Subject: Re: Supervisor hierarchy question
> 
> 
> > Torbjorn,
> >
> >  You can always use the ODBC stuff provided with the erlang/OTP
> > distribution. I needed something a little closer to the 
> wire and with
> > a few extra options. Thats the main reson I implemented my own.
> > Otherwise, the erlang ODBC stuff works just fine.
> >
> >
> > On Tue, 18 Jan 2005 23:19:51 +0100, Torbjorn Tornkvist
> > <tobbe@REDACTED> wrote:
> > > Eric Merritt wrote:
> > >
> > > >Parts of it would. The connection pool specific stuff 
> would work just
> > > >fine. However, my connection directly implements 
> postgresql's version
> > > >3 protocol so it wouldn't be able to speak to mysql. However, if
> > > >someone is willing to implement the mysql protocol I am more then
> > > >happy to work with them to develop a consistant api.
> > > >
> > > >
> > > Ok, I don't know (yet) what that protocol consist of, but 
> I think it
> > > could be of interest to be able to access mysql from Erlang.
> > > Any pointers where to look ? I guess I should browse around
> > > mysql.com... ;-)
> > >
> > > Cheers, Tobbe
> > >
> > > >
> > > >On Tue, 19 Apr 2005 00:30:55 +0200, Torbjorn Tornkvist
> > > ><tobbe@REDACTED> wrote:
> > > >
> > > >
> > > >>Would this code work with mysql as well ?
> > > >>
> > > >>Cheers, Tobbe
> > > >>
> > > >>Eric Merritt wrote:
> > > >>
> > > >>
> > > >>
> > > >>>That would actually rock. Its part of a larger 
> codebase that I havn't
> > > >>>decided whether or not to open up. However, I have no 
> problem at all
> > > >>>opening up the postgresql stuff. If you would like I 
> will grant you
> > > >>>access to the subversion repository.  If you can't get 
> a subversion
> > > >>>client I will post it on the web somewhere. I don't 
> actually expect
> to
> > > >>>get the driver to a usable state before the end of the week.
> > > >>>
> > > >>>
> > > >>>On Tue, 18 Jan 2005 15:48:06 +0000, ernie.makris@REDACTED
> > > >>><ernie.makris@REDACTED> wrote:
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>>Hi Eric,
> > > >>>>
> > > >>>>I read the message about creating a client for 
> postgresql in erlang.
> I am interested in helping you out, as I use postgresql from 
> erlang and
> would be interested in such an interface. Can you post the 
> code? I can help
> you test it if you'd like.
> > > >>>>
> > > >>>>Thanks
> > > >>>>Ernie
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > I'm a programmer, I don't have to spell correctly; I just have to
> > spell consistently
> 



 NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.