Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:14858
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20050212090244.59428.qmail@lists.php.net>
To: internals@lists.php.net
Date: Sat, 12 Feb 2005 09:07:29 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040803
MIME-Version: 1.0
References: <4e89b4260502111655215a94e8@mail.gmail.com>	<20050212074627.64626.qmail@lists.php.net> <4e89b426050212001234271b83@mail.gmail.com>
In-Reply-To: <4e89b426050212001234271b83@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Please test PDO
From: lester@lsces.co.uk (Lester Caine)

Wez Furlong wrote:

> You're missing the point.

No *YOU* are missing the point.

ADOdb is a well established abstraction layer. There have been many 
other attempts to provide the same facilities ( e.g PearDB ) and they 
are all playing catchup. ADOdb tries to assist by mapping functions so 
that people can move between these different layers without difficulty. 
(It has a Pear 'personality')

JOHN has been trying to address the problem of speed of the core generic 
functions - which is the area that PDO is ALSO addressing.

> If you want a database abstraction layer, stick with ADOdb and let
> John adapt that to run on top of PDO.

GERRRR!!!!!!
WHY BOTHER !!!!
Can't we pull together and push towards a SINGLE standard abstraction 
layer, rather than seemingly playing with bits and creating MORE work 
adapting perfectly stable code.

> WHY can't you be bothered to read the resources I've pointed you all
> at, where I explain this?

Because *I* am trying to open the debate as to why we are forcing more 
modules into PHP that do not seem to have been fully thought out. If the 
effort put into PDO had been directed to the core of ADOdb we would HAVE 
all the functionality of PDO - WITH the remaining problems being 
addressed as well and a path to generic database generation. Instead 
work has now got to go into 35 drivers in ADOdb as well as the core 
library *IF* PDO is to be used.

Until PDO has all the same drivers - ADOdb would become a mess, so there 
is little incentive to start changing, and to be honest, you would have 
to PROVE that PDO is as fast as the raw database drivers to warrant a 
change from them.

You are hassling us to test PDO - I am saying hang on - what are we 
testing and is it the right approach anyway? WHY do people want cross 
engine support, so they can move code seamlessly between engines when 
the customer insists that 'X' is the only engine they will use. PDO is 
NOT addressing that problem. Your SQL code will still be engine 
specific, and the bulk of the changes will be in that area. So people 
need to be aware of *ALL* the limitations of PDO before they spend too 
much time going down a potential dead end!

At the present time PDO is not suitable for me and just seems to be a 
waste of expertise that could be directed to something much more useful 
such as improving the core performance of ADOdb :(

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services