Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9842
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <40A39B11.2000201@backendmedia.com>
Date: Thu, 13 May 2004 17:58:09 +0200
Organization: BackendMedia GbR
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
MIME-Version: 1.0
To: Marc Boeren <m.boeren@guidance.nl>
Cc: PHP Development <internals@lists.php.net>
References: <0C77C7530EA52A4EBD1C47C80D1D291E07F8D5@sbs.GuidanceBV.local>
In-Reply-To: <0C77C7530EA52A4EBD1C47C80D1D291E07F8D5@sbs.GuidanceBV.local>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PDO (was: SQLite API deficiency)
From: smith@backendmedia.com (Lukas Smith)

Marc Boeren wrote:

>>I'm currently in DB API mode (working on PDO), 

> I know PDO is slated to be _the_ db-abstraction module from 5.x (5.1?)
> onwards (which would replace dbx, but that's fine by me: PDO seems to
> work more or less the same but with a more OO-ish api), but I was
> wondering if these names bear any relation to the Python DB-API and the
> Python Database Objects, or if that is more of a coincidence?
> 
> Also, will there be an complementary SQL-abstraction package for
> SQL-dialect differences (such as UPPER(value) vs. UCASE(value), or
> differences in TOP/LIMIT/OFFSET usage)? 
> I have a preliminary package ready (in php-source-code, not c) that is
> coupled to an OO-ish api for dbx, but is easily rewritable to a more
> generic version.

Actually PDO is more an API unification than abstraction layer. 
Abstraction will best be handled in userland code, specifically a PEAR 
package should handle this. For this reason I am also involved in the 
project more from the API perspective then from actual C implementation. 
Also obviously the current DBAL in PEAR have solved alot of the issues 
that PDO faces as well.

regards,
Lukas Smith