From: gabriele renzi <surrender_it@...1.vip.ukl.yahoo.com>
Date: 2004-01-10T06:31:38+09:00
Subject: Re: Database applications and OOness

il Thu, 8 Jan 2004 09:50:14 +0100, "Robert Klemme" <bob.news@gmx.net>
ha scritto::


>
>What exactly is the difference between the "shared and abstract ruby/DBMS
>api" and DBI?  IMHO DBI is exactly an abstract DBMC API, albeit only for
>relational databases.  Do you want to unify the different SQL dialects?
>Or do you want only certain things unified, e.g. date and time formats
>(like JDBC tries with its escape sequences)?

actually, I meant having at least a JDBC like interface, or, what in
python is the DB-api (I suppose).
I mean, if you have to connect to various db you may find:

# first find in google for each dbms
PGconn.connect "localhost", 5432, "", "", "test1"
ORAconn.logon "foo", "bar", "db"
Mysql.new host, user, passwd
Interbase.connect database,username,password,charset


Now, I know different dbms have different features, but ate least some
convention on a basic set of available methods would be good. 
If we, as a community, could agree on a general dbms interface (dbi
fits well to me :) hat would be better than a separate wrapper
package.

ATM, Joe De Veloper has to choose beetween dbi-api, DBMS-foo api,
DBMS-bar api. Then he have to get DBMS-(foo|bar) api, dbi wrapper,
and finally start coding.

With a common api Joe just download a binding, find an already common
and documented interface,  and start coding. 
Then if he want to switch to DBMS-bar he could have (potentially)
working code without the need for changes.

Obviously just in a ideal world :)