Re: RFC: ext/mysql deprecation

On 12 November 2012 21:48, Johannes Schlüter <johannes.schlueter@oracle.com> wrote: > On Mon, 2012-11-12 at 21:00 +0800, Adam Harvey wrote: >> 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 > > Short comment: Those will mostly be unseen. Most people use the @ > operator to silence errors on these functions, so such deprecation > notices would go unseen. There are some users we're never going to reach, short of removing the functions altogether. It's the same for everything we deprecate or remove — the screaming about ext/sqlite being removed in 5.4 is still there, for instance, and will probably only increase as distros roll out 5.4 packages. A five second Google Code Search suggests the ratio of suppressed calls to mysql_connect() to unsuppressed ones is about 2:11*, at least within its increasingly out of date corpus. Admittedly, many of the users of the unsuppressed code aren't going to have error reporting turned on anyway, but I don't think the situation's dire. All that said, is there a different function we could hook into that does make more sense? Adam * No statistical validity claimed. I'm not Nate Silver, nor do I play him on TV.