[erlang-questions] What is the status of ebdc?
Wed May 20 21:46:00 CEST 2009
I am still researching some of the erlang-mysql modules. But there are
some questions that cannot be answered.
1. Which is the latest version of any module. Everyone seems to be
modifying the Process-one module which looks to be old. The others are
not any younger. As far as I can tell they are all three years old.
MySQL and SQL server have changed a lot since.
2. There are no bug trackers for any of the projects although many are
moving projects to github the issue queues are empty.
So which is the latest and best connector?
On Wed, May 20, 2009 at 9:24 PM, Jon Gretar Borgthorsson
> On Wed, May 20, 2009 at 7:13 PM, Carl McDade <> wrote:
>> Yes but unlike Apache Yaws provides an application layer
>> (yapps,appmods,yaws pages...) but nothing to connect to a RDBMS.
> True.. true...
>> If you are starting a project from scratch and only using Erlang then
>> this is okay. But I think the reality is most will be migrating from
>> another technology or data source.
> And I would exactly think that having the DB layer seperate helps with this.
> I have dealt with connecting legacy data to Rails and it can be great pain
> because everything in Rails assumes you use ActiveRecord and ActiveRecord
> assumes many other things. Thus making things even harder by constantly
> assuming the wrong things about my data and what I want.
> I prefer the Nitrogen way. Having a simple open structure that you can
> connect whatever database layer you wish to use.
>> Just think about how many would choose Nitrogen over Rails (like me)
>> if they did not have to worry about re-designing the database. Many
>> CMS and other web application might be built on Nitrogen if the web
>> developer only had to connect to a blog or wiki mysql db and start
>> building from there.
> There is nothing that stops you from getting the erlang mysql module and
> making a thin wrapper and connecting that blog database to a Nitrogen page
> using the simple binding system Nitrogen uses. It's really barely an hours
> work to write this wrapper. It's how most people did things before Rails. :)
Content Management Systems Consultant
More information about the erlang-questions