Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64024
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.185 cause and error)
Message-ID: <50ACA227.9080305@lsces.co.uk>
Date: Wed, 21 Nov 2012 09:43:03 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120826 Firefox/15.0 SeaMonkey/2.12
MIME-Version: 1.0
To: "internals@lists.php.net" <internals@lists.php.net>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com> <CACwt+JeLin8aLtmBedO+DnJ4cz0Ajb75depkd7v_QK1NORUPOg@mail.gmail.com> <CADajX4CmOEBy3aZOh+qpfmq=OTiLF6+EuOyiRWM2bx7JxZumrg@mail.gmail.com> <50A9F799.5080909@codeangel.org> <CADajX4CbLLagJnO+dkZsGXkaS8h7rabtmpOz6Gos0KqcHOpsMA@mail.gmail.com> <CAAyV7nF3VyvCa_YCYrtaajm8b8CpTCUq7M6=07hJ5eCGBaUZrA@mail.gmail.com> <CADajX4AxoK73x-CoJx71j6g3ndiMbF2LYhnLrs2p_CcOBxmgjQ@mail.gmail.com> <50AC60BC.1030207@gmail.com> <CADajX4AtDA6i1Xr0voT5gke+qtPaxu3Yh-6wGvuLQf-o8UBwKQ@mail.gmail.com> <50AC6D70.3080303@gmail.com>
In-Reply-To: <50AC6D70.3080303@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: lester@lsces.co.uk (Lester Caine)

David Muir wrote:
> No other extension was deprecated before moving to PECL, so why the extra hurt
> for ext/mysql? As I've said before, it doesn't makes sense to have it throw
> notices while it's in core, then no longer throw notices once moved to PECL. If
> the plan is to drop it completely, and not move it to PECL, then deprecation
> notices do make sense as there's no other recourse once the extension is removed.
>
> In that case we really should have 3 questions:
>
> Should ext/mysql generate E_DEPRECATED notices in PHP 5.5? (yes/no)
Not that I'm allowed, but the more I look at this 'no' is the right answer!

> Should ext/mysql be moved to PECL or dropped completely in the future
> (PECL/dropped)
Since most distros DON'T follow the bundling that PHP itself proposes they will 
continue to include mysql anyway? The situation would then be no different to 
that when mysql was dropped as enabled by 'default' and so users had to be TOLD 
how to enable it again. THIS is the point at which mysqli is then recommended as 
an alternative?

> Should the manual text be changed to make soft deprecation clearer? (yes/no)
There is some good 'upgrade' documentation. If that is not going to be brought 
up to date where it is currently, could the author/owner be asked to allow it to 
be moved to php.net where it can be used as the base for that essential guide? 
My own interest here is that I NEED a good reference to make the changes needed 
for sites and so people are saying that the currently identified document is out 
of date?

If distros add mysql into their installations going forward it is their problem 
to maintain it. Just the same as other extensions that are still available via 
the same route?

Including mysql in the windows distros is probably where most new users will be 
starting from? So again not enabling them is another flag point ...

-- 
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