Re: Re: cvs: pear /DB/DB dbase.php fbsql.php ibase.php ifx.php msql.php mssql.php mysql.php mysqli.php oci8.php pgsql.php sqlite.php sybase.php
| From: | Lukas Smith | Date: | Fri, 26 Nov 2004 09:46:03 +0000 |
| Subject: | Re: Re: cvs: pear /DB/DB dbase.php fbsql.php ibase.php ifx.php msql.php mssql.php mysql.php mysqli.php oci8.php pgsql.php sqlite.php sybase.php | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-34575@lists.php.net to get a copy of this message | ||
Daniel Convissor wrote:
Sir Lukas: On Thu, Nov 25, 2004 at 11:58:56PM +0100, Lukas Smith wrote:Hmm I wonder if it wouldnt make more sense to have separate drivers for these cases. Even with odbc we could provide a odbc_db2 driver. Then again I am looking at this from the MDB - i want to abstract everything - view point where the number of if statements are going to be much more numerous depending on the different RDBMS. Then again most of the stuff that goes beyond what PEAR DB does is in separate modules which can handle different versions already.phptype(dbsyntax)://... It's mainly to differentiate between DBMS sub-types when it matters. Examples: odbc(db2)://... ibase(firebird):// But it can also be used for versions: pgsql(8.0)://... (not that this exists in DB yet)Log: * If DSN contains "dbsyntax", always use that for $this->dbsyntax.whats the purpose of dbsyntax?
It seems better for the user to tell us what to expect rather than doing yet more crazy magic that may or may not work and add unnecessary overhead.I agree regards, Lukas