Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63968
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.214.170 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <50A9F799.5080909@codeangel.org>
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>
Date: Mon, 19 Nov 2012 19:45:52 +0800
Message-ID: <CADajX4CbLLagJnO+dkZsGXkaS8h7rabtmpOz6Gos0KqcHOpsMA@mail.gmail.com>
To: Chad Emrys <admin@codeangel.org>, Patrick Allaert <patrickallaert@php.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: aharvey@php.net (Adam Harvey)

On 19 November 2012 17:10, Chad Emrys <admin@codeangel.org> wrote:
> On 11/17/2012 08:54 PM, Adam Harvey wrote:
>>
>> On 16/11/2012 8:58 PM, "Patrick ALLAERT" <patrickallaert@php.net> wrote:
>>> Maybe it is worth mentioning in the RFC what the E_DEPRECATED notice
>>> message would look like so that people hiding it know what the plan
>>> is.
>>> e.g.:
>>> "mysql_*() functions are, as of PHP 5.5, deprecated and will be
>>> removed in next major release. Use the mysqli_*() functions instead".
>>
>> Good point. I did put some proposed wording in the patch, but I'll add i=
t
>> to the RFC when I get home tomorrow and am not just on a phone.
>>
> Could we not mention mysqli unless you mention PDO as well?

I've added the wording I put in the patch to the RFC. For the record, it is=
:

"The mysql extension is deprecated and will be removed in the future:
use mysqli or PDO instead"

This is basically a cut down version of the longer message in the
manual on each ext/mysql function, except explicitly noting the
deprecation. I'm not at all averse to adding a link to the Choosing an
API manual page to help developers make an informed choice (and,
ideally, we could beef that up to include more detail on what
migration actually looks like) =E2=80=94 this does feel like something we
could tune after voting on the bigger issue, though.

My intention at this stage is to call a vote next Monday: it feels
like the discussion has mostly died down now (which isn't to say I
think we're at a consensus necessarily =E2=80=94 it just feels as though th=
e
flurry of opinions have been made and argued either way), and I'm
hoping that everyone can have a think about where and how they'd like
to see this move forward (if at all) between now and then. Given we've
only just hit alpha 1, I don't think we need to rush into a decision
right now for the sake of one.

Thanks to everyone so far for their input =E2=80=94 I think it's been a
valuable, productive discussion.

Cheers,

Adam, who is still personally in favour of deprecation. :)