Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4582
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
Date: Thu, 25 Sep 2003 16:22:44 +0200
MIME-Version: 1.0
Message-ID: <3F731654.9443.187A82@localhost>
Priority: normal
In-reply-to: <7BE0F4A5D7AED2119B7500A0C94C58AC3D6D85@DELLSERVER>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Subject: RE: [PHP-DEV]  differences in the RDBMS ext API's
From: fb@fbeyer.com ("Ferdinand Beyer")
References: <7BE0F4A5D7AED2119B7500A0C94C58AC3D6D85@DELLSERVER>

On 25 Sep 2003 at 15:04, Marc Boeren wrote:

> I just skim the php-dev list nowadays, but this seems a bit like what 
the
> dbx extension does (I wrote that). Now I know dbx is just a 
lightweight
> wrapper that doesn't try to emulate specific functionality, and it may 
still
> need some more wrapper functions (like commit/rollback and 
parameter
> binding) and support for more databases and a better efficiency, 
but one
> thing it does is provide a common api and common behaviour for 
all supported
> databases (no, Interbase is not among them, but feel free... :-)

IMO there are some problems with the dbx extension:

- it is a wrapper for PHP modules instead for the underlying 
database API (therefore slower)
- you cannot rely on it if you depend on an ISP that does not support 
this extension
- it does not include a C API that would be useful for custom PHP 
modules to access a database
- it does not include an OOP API

My dream is a "full featured" SQL extension completely replacing all 
other database modules, fast, flexible, build-in by default, 
recommended to be the best way to access databases in PHP.

It should include a C API for extension developers as well as OO 
(like PEAR::DB) and procedural (like mysql ext) PHP APIs.

Just my two cents....

-- 
Ferdinand Beyer
<fb@fbeyer.com>