Re: RFC: ext/mysql deprecation
| From: | Derick Rethans | Date: | Mon, 12 Nov 2012 16:22:40 +0000 |
| Subject: | Re: RFC: ext/mysql deprecation | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63822@lists.php.net to get a copy of this message | ||
On Mon, 12 Nov 2012, Adam Harvey wrote:
> I've written an RFC to cover deprecating ext/mysql in PHP 5.5:
> https://wiki.php.net/rfc/mysql_deprecation. While we handled
> the soft
> deprecation in the documentation purely via a straw poll on Internals,
> I presume this will end up needing to go to a vote, hence the RFC.
>
> I won't rehash the background overly (there's some more detail in the
> RFC), other than to note that we've now had deprecation notices on all
> mysql_* functions in the manual for about six months and that the
> logical next step is to start generating E_DEPRECATED notices when
> users connect via mysql_connect(), mysql_pconnect() or the implicit
> ext/mysql connection routines. It's my belief that doing so will
> hasten the move of users to the more modern (and supported) APIs
> available: mysqli and PDO, and that this process will also likely
> encourage some users to switch to safer patterns such as prepared
> queries at the same time.
>
IMO, there doesn't need to be a discussion on *how* to deprecate
ext/mysql. We have E_DEPRECATED for that, just like you write in your
RFC. The only question is "do we want
to deprecate it?". On that one: +1
cheers,
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
Posted with an email client that doesn't mangle email: alpine