This driver is "safe" in the sense that it's used by ErlyWeb so whenever an ErlyWeb app needs a feature or a bug fix it will be applied to this driver. However, this driver has been stable for a while except for a few patches here and I think it should work well for you. If you find some issue, you have the source code, which is not that big, so it shouldn't be that hard to fix.
Yariv On Tue, Sep 23, 2008 at 1:15 AM, Alex <[EMAIL PROTECTED]> wrote: > > Hello List, > > I came to this list because of the Erlang mysql driver. In my current > project, I need to connect to a MySQL database (several actually), > running version 5.1. > Development is on MacOSX, deployment is on Linux. > > I understood that the erlang-mysql-driver found in google code > (revamped mysql driver) is used by ErlyWeb. > If this is correct, does this mean it is a "safe" way of connecting to > MySQL from Erlang, even when not using ErlyWeb? By "safe" I mean, is > this code evolving with ErlyWeb or is it a "dead end" (just an > experiment or something equivalent)? > From my small test, it works fine so I am eager to use it. The other > two alternatives would be ODBC or the "original" driver I found at > ProcessOne. > ODBC does not make much sens if there is a native driver available. > The driver at ProcessOne seems used for ejabberd but seems to lack > some features added by Yariv. > > Any info appreciated ! > > Alexander > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
