RDBI is a rewrite of the notable Ruby/DBI database interface library,
and is largely complete at this point. It sports a few new ideas, but
those of you familiar with Ruby/DBI or perl's DBI would be unsurprised
at its API, which has been trimmed heavily to a minimal set of calls.

I desperately would like to position this as a compelling alternative in
the middle to the current situation of our database layers being borne
of several independent APIs that merge into some huge library that does
a lot more than process data queries. A more unix philosophy of small,
interchangeable parts doing the right things, if you will. Another
person coined it as a "potential rack for databases", and I think that
makes a lot of sense in retrospect.

So, what I'd like, and have been pushing on various places in IRC and in
local user groups, is some honest criticism on where it is and where it
can go. Documentation is currently weak largely because I'm waiting for
commentary like this to shape the final product. You'll need to be able
to read the code.

We have various plans such as async support and the library is largely
thread safe, if coarsely grained. There is a sqlite3 driver that is
working and is mildly tested.

I would like to get things documented a little more, and to RC within
the next two weeks. Any assistance you can provide as a group would be
great.

http://github.com/erikh/rdbi
http://github.com/erikh/rdbi-dbd-sqlite3 # sqlite3 driver.

Thanks for your time,

-Erik
-- 
Posted via http://www.ruby-forum.com/.