Create an SQL backend about qu

[laserlemon]

What's wrong with using activerecord? It's familiar and well-tested. Or you could drop to the arel level.

[bkeepers]

Nothing, really. It'd just be nice to get closer to the driver if possible. I realize that's a lot easer with redis and mongo than it is sql databases, so might just have to settle for ActiveRecord.

[danielmorrison]

Bonus points if you call the gem 's-qu-l'

[bkeepers]

or se-qu-al

[luislavena]

What about using DataObjects and do_* adapters instead? they offer an standardized interface to different databases.

[bkeepers]

Does it play nice with ActiveRecord? I'd probably prefer to have two separate backends, one for DO and another for ActiveRecord.

[luislavena]

DataObjects powers DataMapper but is not DataMapper. Think of it as the newer DBI.

I thought you wanted a SQL close to the metal as possible, not a pluggable one that you can change the model for one in your current application (mostly using ActiveRecord-users).

[bkeepers]

Gotcha. I do prefer something closer to the metal. I've never used it. I'm not opposed to having a qu backend for it if people would use it.

[jnunemaker]

Certainly not opposed to this, but I am not interested in maintaining it. If anyone tackles this, just do it in your own repo/gem (qu-sql, qu-ar, etc.).