On Nov 15, 2012, at 22:28, Will Fitch <wfi...@meetme.com> wrote: > Your argument is valid. The question of, why do we deprecate something > that is so heavily used comes to mind, but in the end, this is a something > the extension maintainers want - not end users. Maybe the correct solution > is to hand off the maintenance of this extension to a new team? > Your argument is valid. The question of, why do we deprecate something > that is so heavily used comes to mind, but in the end, this is a something > the extension maintainers want - not end users. Maybe the correct solution > is to hand off the maintenance of this extension to a new team?
There isn't much maintenance needed. For a few years already ext/mysql isn't receiving new features and bug inflow is low. Thanks to mysqlnd we have to fear libmysql changes way less these days. We, from the MySQL Connector Team at Oracle, add new features to mysqli (and eventually PDO) only, though, for quite some time already. Bugs in ext/mysql are being fixed in a best effort way and we plan to do this as long as required by the community. Users should use mysqli for having access to everything MySQL has to offer. Officially deprecating mysqli is, in my opinion, mostly a help for users to go in the "correct" direction early instead of struggling due to missing features later. johannes -- Johannes Schlüter, MySQL Connectors Team, ORACLE Corporation Note: The above is no legally binding promise by Oracle. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
