On Sat, 5 May 2001, Benjamin J. Tilly wrote:

> >===== Original Message From Steve Tuckner <SAT / MULTITECH.com> =====
> >There is currently an effort underway to define a standard DBI interface for
> >Ruby and a mailing list for this effort.  Please go to groups.yahoo.com at
> >http://groups.yahoo.com/group/ruby-dbi-talk to join this mailing list.
> [...]
>
> Sorry, I don't have any energy to devote to this effort.
>
> But note that Ruby should not necessarily (IMHO) just
> lift the overall design of DBI.  Its purpose is to
> create an abstract interface for lots of databases.
> But  Ruby has a built-in facility for defining abstract
> interfaces.  They are called modules.  So I suspect that
> the best approach is to make DBI a module that is
> included into each driver.  Then people would load the
> drivers and send requests there, but the methods that
> people would access would be the ones from the DBI
> module...

You could still use a DBI class whose connect is a factory method which
churns out objects which include the DBI_interface module, maybe?

The perl DBI model is nice in that you only mention DBI explicitly, the
driver is loaded once the connect arguments are known.

Just a post prandial thought,

Mike

-- 
mike / stok.co.uk                    |           The "`Stok' disclaimers" apply.
http://www.stok.co.uk/~mike/       |
GPG PGP Key 1024D/059913DA         | Fingerprint      0570 71CD 6790 7C28 3D60
stok / colltech.com (CT - work)      |                  75D2 9EC4 C1C0 0599 13DA