PHP has long suffered from poor implementations of some of the DB extensions and good implementations of others. PDO is a good opportunity to unify the extensions and have a common code base so that bug fixes propagate to all extensions (at least in most cases). Of course there are also additional benefits to PDO.
I think PDO is very important for the future and stability of PHP and I don't think projects like ADOdb are replaced by it. But yes, I think in the long-term ADOdb will probably be better off migrating to PDO for it's underlying DB connections. It would probably improve it's maintainability and stability.
Andi
At 03:12 AM 2/12/2005 -0500, Wez Furlong wrote:
You're missing the point.
PDO isn't a replacement for ADOdb, it's a future replacement for ext/mysql, ext/pgsql, ext/oci8, ext/odbc, etc. etc. etc.
If you want a database abstraction layer, stick with ADOdb and let John adapt that to run on top of PDO.
WHY can't you be bothered to read the resources I've pointed you all at, where I explain this?
--Wez.
On Sat, 12 Feb 2005 07:51:13 +0000, Lester Caine > Wez > I have had a look at PDO, but for many of us it is just a step BACK to > the bad old days. > ADOdb is well established and works. If you use the accelerator module > then it can be very fast. WHY couldn't John have been helped to convert > it to a more integrated package when he tried to get help from this > list, which would allow upgrades to MANY systems without major > re-writing of their code bases? > OK many base functions will do the same job, but there is several years > of development in the extensions to ADOdb, all of which would need to be > re-done to switch to PDO - which is only recreating some of the > functionality of the ADOdb drivers.
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
