Re: Re: cvs: pear /DB/DB dbase.php fbsql.php ibase.php ifx.php msql.php mssql.php mysql.php mysql4.php oci8.php odbc.php pgsql.php sqlite.php
sybase.php
| From: | Pierre-Alain Joye | Date: | Fri, 02 Jan 2004 17:04:22 +0000 |
| Subject: | Re: Re: cvs: pear /DB/DB dbase.php fbsql.php ibase.php ifx.php msql.php mssql.php mysql.php mysql4.php oci8.php odbc.php pgsql.php sqlite.php sybase.php |
||
| References: | 1 2 3 | Groups: | php.pear.cvs php.pear.qa |
| Request: | Send a blank email to pear-qa+get-322@lists.php.net to get a copy of this message | ||
On Fri, 2 Jan 2004 11:58:49 -0500
Daniel Convissor <danielc@analysisandsolutions.com> wrote:
> Not really. Some DBMS's already lowercased keys when in portability
> mode but others did not. Thus, it wasn't REALLY portable. Now it is.
> The
> point of lowercasing keys is to make all DBMS's behave the same, which
>
> means portability, hence the option name is appropriate -- let alone,
> that's the name that was already in use for this functionality for
> some DMBS's.
>
> This was discussed in a thread on pear-dev entitled "PEAR::DB and
> oracle question."
It is definitively an huge BC.
We are not talking about what's is the best way to implement the
'portability' flag but about how these methods work before.
Again, howmany users of DB with mysql backend? 80%? 90%? And how many of
them use the portability flag with uppercase column names?
Alan's suggestion is the way, imo.
pierre