Re: RFC: ext/mysql deprecation

Leigh wrote:

Hi On 13 November 2012 00:29, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

That is simply not true. If you download PHP and do ./configure && make install you do not get MySQL support. You have to explicitly specify that you want it.

My apologies then. I actually checked a ./configure output, and saw under Configuring extensions "checking for MySQL support... no" I assumed it was going to try to enable it if it was available. Lots of other extensions have the wording "checking whether to enable", which is why I differentiated it from those. On 13 November 2012 09:03, Lester Caine <lester@lsces.co.uk> wrote:

YES people can simply switch off the checks, but again that misses the whole problem! Having switched off the checks - you have no idea what is about to blow up.

If users wish to deliberately ignore (or worse, specifically disable) informative messages during development, that is their own problem. When ext/mysql is finally removed, nobody will be able to say they didn't have enough warning.

Leigh - the point here is that the vast majority of users know nothing about this! Their ISP has had to switch E_DEPRECATED off for all of their users simply to keep legacy sites running. 'Not our problem' is the wrong stance with so many people reliant on PHP's infrastructure.

The sooner we get this warning out there (i.e. E_DEPRECATED + message in the documentation starting with 5.5), the sooner wider community can start adjusting for it. There is no point delaying it as much as possible. As Sherif said, there has been far too much procrastination on the subject already. Lets get E_DEPRECATED in for the first RC so all of the social-focused php sites can get their rants out early, and get a few users thinking about the future of their codebases as soon as possible. Maybe even some of them will decide to contribute back and write some adoption guides and/or cheat sheets.

The problem will remain as to who helps the vast majority of users who are using sites that simply work for them. The problems making legacy code work with PHP5.4 are small compared with converting many millions of sites that currently use MySQL simply because that is all their ISP's provide, and the code running their site was probably installed from examples that only ever used 'mysql_' ... It's simply not practical to strip all of these old code examples from the internet, so it IS important that new examples are activly published by everybody to swamp what is now very out of date material. Many of the sites I'm currently porting from a number of ISP's have needed a lot of work to tidy them up to run on a new set-up, and there was no way their owners could ever have done that themselves! And I'm moving them to Firebird anyway so no problem with MySQl code, but I do have a couple of big sites that ARE running on mysql_ so I will need to address them at some time. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk