Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63920
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain oracle.com designates 156.151.31.81 as permitted sender)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com> <50A10A9D.9070402@oracle.com> <CAAyV7nF2tt6HtFZKevH_2kknqOvEmLJjEOF2_Bn_VHaZFUJERw@mail.gmail.com> <CAPwsocH3_qHSZbLFe27qX+KgBAC1D8KhwLi+PLHW503sCTBtTw@mail.gmail.com> <50A1946F.8010407@lerdorf.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> <50A54C7F.6020701@lerdorf.com> <CAArmra3tCz3MZNB8KT5h29vWbvg56EjaaO8sNQ4hvpK+Yp!
 x4HA@mail.gmail.com>
In-Reply-To: <CAArmra3tCz3MZNB8KT5h29vWbvg56EjaaO8sNQ4hvpK+Ypx4HA@mail.gmail.com>
Message-ID: <E5623144-ECB0-4B68-8260-6E1FEECBAF10@oracle.com>
Date: Fri, 16 Nov 2012 08:38:19 +0200
Cc: Rasmus Lerdorf <rasmus@lerdorf.com>,
        Stas Malyshev <smalyshev@sugarcrm.com>, Adam Harvey <aharvey@php.net>,
        Devis Lucato <devis@lucato.it>,
        PHP Developers Mailing List <internals@lists.php.net>
To: Will Fitch <wfitch@meetme.com>
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: johannes.schlueter@oracle.com (=?utf-8?Q?Johannes_Schl=C3=BCter?=)

On Nov 15, 2012, at 22:28, Will Fitch <wfitch@meetme.com> wrote:
> Your argument is valid.  The question of, why do we deprecate something
> that is so heavily used comes to mind, but in the end, this is a something=

> the extension maintainers want - not end users.  Maybe the correct solutio=
n
> is to hand off the maintenance of this extension to a new team?
> Your argument is valid.  The question of, why do we deprecate something
> that is so heavily used comes to mind, but in the end, this is a something=

> the extension maintainers want - not end users.  Maybe the correct solutio=
n
> is to hand off the maintenance of this extension to a new team?

There isn't much maintenance needed.

For a few years already ext/mysql isn't receiving new features and bug inflo=
w is low. Thanks to mysqlnd we have to fear libmysql changes way less these d=
ays.

We, from the MySQL Connector Team at Oracle, add new features to mysqli (and=
 eventually PDO) only, though, for quite some time already. Bugs in ext/mysq=
l are being fixed in a best effort way and we plan to do this as long as req=
uired by the community.

Users should use mysqli for having access to everything MySQL has to offer.

Officially deprecating mysqli is, in my opinion, mostly a help for users to g=
o in the "correct" direction early instead of struggling due to missing feat=
ures later.

johannes
--=20
Johannes Schl=C3=BCter, MySQL Connectors Team, ORACLE Corporation
Note: The above is no legally binding promise by Oracle.