Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63903
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.216.49 cause and error)
Message-ID: <50A59E24.4060704@lerdorf.com>
Date: Thu, 15 Nov 2012 18:00:04 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: Sherif Ramadan <theanomaly.is@gmail.com>
CC: Anthony Ferrara <ircmaxell@gmail.com>, Will Fitch <willfitch@php.net>, 
 Stas Malyshev <smalyshev@sugarcrm.com>,
 Adam Harvey <aharvey@php.net>, Devis Lucato <devis@lucato.it>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com> <CAAyV7nFOGa7UVALSQyAs-A+R0kuEmXoHPrxvCXNBnzAxLy0dww@mail.gmail.com> <50A2D672.7010600@gmail.com> <50A30144.5070305@phpgangsta.de> <50A3BEC0.8030607@gmail.com> <CAET_qdMmhRyidM6_VOokBu6tYvgrPHMOPdzz0PaFpxc3NaTdYQ@mail.gmail.com> <CADajX4Bh+5YrCPEFLzC2qqeJ4NnADbBV0u+wByz3Kb7Jp45KOw@mail.gmail.com> <50A54713.8090102@sugarcrm.com> <CAArmra2bjj3y2UUV8nszU74tN9o4VvB67aXzq5Z1cE2Y_tVijg@mail.gmail.com> <50A549EB.2020408@lerdorf.com> <CAArmra2BCmbOjkK0D8gKc5o0Pwhx0jNGi-3m2C2Z2dAnb0yv7w@mail.gmail.com> <CAAyV7nGMi20xjBYbouvsyUrxdOSuboP6u-guY9DX8qkSagQbjg@mail.gmail.com> <CAL+t6cEfDPT_-td5Ts4-SpNowSK9GJAq71KPKU-5ZUP2yzsNjw@mail.gmail.com> <CAAyV7nF=gMzD6rHUW2mffXv9uc-sSuO3cX=kyMnt81bUZH_VtQ@mail.gmail.com> <CAL+t6cFY5vPERz58foLh01ori68euYbSg-LGcjOsm9cgeNAs2A@mail.gmail.com> <50A58828.4070701@lerdorf.com> <CAL+t6cEZur=Eig6+0LzrdOWRRonSbUGV-eMeg7iyMA2bcZrvwA@mail.gmail.com>
In-Reply-To: <CAL+t6cEZur=Eig6+0LzrdOWRRonSbUGV-eMeg7iyMA2bcZrvwA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: rasmus@lerdorf.com (Rasmus Lerdorf)

On 11/15/2012 05:52 PM, Sherif Ramadan wrote:
> This was the soft-deprecation notice that I believe was discussed
> before the actual steps were to be taken to officially deprecate
> ext/mysql. Yes, it's a suggestion, but a clearly worded suggestion,
> none-the-less. It has been around for a little over 5 months now. I
> think that's plenty of time to start alerting people to the fact that
> the deprecation is coming.

5 months is nothing in PHP land when it comes to a feature like this.
Like Anthony said, this is something that needs to be front and center
everywhere. And like David said, it doesn't actually make much sense to
deprecate the functions themselves. The extension is going to be moved
out of core eventually, but if you still choose to use it by getting it
from pecl throwing deprecation warnings from each call makes no sense.

We need a frontpage notice. A big notice in the next UPGRADING file.
There was nothing about this in the 5.4 UPGRADING file, for example. We
also need tutorials showing how to migrate from mysql to mysqli and
conference talks on the same showing some of the cooler things like
async queries that you get by moving to a more modern API.

-Rasmus