Derick Rethans wrote:
1. ADOdb has *nothing* to do with the PHP project
It would not exist without it. No reason why it could not be part.
Yes ADOdb is large, and that is part of the point. The core needs help from PHP to become lean, and then the extensions are just bolt-ons to a lean core. PDO should be that core, but I'm not seeing that at the moment. I'm seeing 'BDE' all over again. An attempt at a flat world view of databases that eventually died because it lost all abbility to also surface the strengths of the engines it was accessing.2. Some people don't need bloated libraries as ADOdb and still want to have one single unified interface to databases - THAT is what PDO is for: raw access.
ADOdb has a C accelerator that would benefit from the same sort of work that has been put into PDO - it's an existing project.Again, ADOdb is a PHP USERLAND solution, PDO is not. PDO is C, PDO is no bloated OO, PDO is fast.
My particular problem is mapping the SQL scripts between engines. That requires access to functions that PDO - I now learn - is not planned to provide. So *PLEASE* remember telling us what something will NOT do is as important as pushing what it does.Feel free, I don't care what you want to use - if you don't care about PDO, fine with me, good luck with ADOdb.
Wez has already said what he does not plan to do with PDO - and that causes problems switching the next layer applications TO it. So we still need to plug that hole - PDO will not do it :(
-- Lester Caine ----------------------------- L.S.Caine Electronic Services
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
