RE: [PHP-DEV] differences in the RDBMS ext API's

From: Date: Thu, 25 Sep 2003 14:22:44 +0000
Subject: RE: [PHP-DEV] differences in the RDBMS ext API's
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-4582@lists.php.net to get a copy of this message
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>

« previous php.internals (#4582) next »