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
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
