Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63898
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain roshambo.org from 209.85.220.42 cause and error)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
In-Reply-To: <50A58828.4070701@lerdorf.com>
Date: Thu, 15 Nov 2012 17:14:38 -0800
Cc: Sherif Ramadan <theanomaly.is@gmail.com>,
 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>
Content-Transfer-Encoding: quoted-printable
Message-ID: <A6B78A67-5295-42CB-9F2B-4535442027E6@roshambo.org>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com> <50A20CCB.8090909@lsces.co.uk> <8A8A29F9E43E417FB5450D63019B2DDB@NeiRoze> <8f4231fc-6e3c-4a33-af71-2af5e7a95dfd@email.android.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>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: philip@roshambo.org (Philip Olson)


> The main argument is that we haven't actually made it clear in the
> manual that the extension is going to be deprecated. There is a user
> note on http://www.php.net/manual/en/book.mysql.php and a "This
> extension is not recommended for writing new code" on
> http://www.php.net/manual/en/intro.mysql.php
>=20
> As Anthony mentioned, this is a very weak best-practice type of =
message
> that we are only barely whispering here. To go from that to start
> throwing deprecation warnings on what is perhaps the most heavily used
> PHP extension ever is a rather drastic step. Your argument seems to =
be,
> "Well, there is no point documenting it because people won't read it
> anyway", which may be true, but we haven't actually tried that yet and
> for something like this I think it should be the first step.


I wanted to clarify that it was intentional to not use the word=20
"deprecated" in the documentation because it's not deprecated. However,=20=

the documentation for *every* ext/mysql function begins with a pink box=20=

that says it's discouraged, and these boxes suggest alternatives via=20
mysqli/pdo_mysql.

Whatever the case, we'll update the documentation now. It'll clarify =
that
one day this extension will be deprecated. The only question here is the=20=

"how" and "when" but that's not a showstopper for the docs.

As for the ext/mysql->mysqli conversion script. It's outdated and =
difficult=20
to find but we'll make an official php.net version and promote/update it =
so=20
eventually it'll become awesome. It's certainly not ready today. I =
suspect
people will also want an ext/mysql->pdo_mysql version. No promises =
there=85 :)

Regards,
Philip