Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63844
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.219.42 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <8f4231fc-6e3c-4a33-af71-2af5e7a95dfd@email.android.com>
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>
Date: Wed, 14 Nov 2012 00:13:26 +0800
Message-ID: <CADajX4AESkqQNkQRgErjWaXEBEMEf_Mu9xTNG3ZEcPPgJ1Jyow@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Reinis Rozitis <r@roze.lv>, PHP internals <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 13 November 2012 23:49, Johannes Schl=C3=BCter <johannes@schlueters.de> =
wrote:
>
>
> Reinis Rozitis <r@roze.lv> wrote:
>
>>> Rewriting perfectly functional mysql code to use mysqli is not a
>>trivial
>>> move, just as are the problems of  re-writing PHP5.2 code to work
>>cleanly
>>> on 5.4. ISP's are stuck between keeping customers - who are most
>>likely
>>> not even very computer literate - working while fighting the problems
>>that
>>> changes such as removing mysql will cause them.
>>
>>
>>I wonder  if there have been any plans or suggestions (while dropping
>>the
>>old ext/mysql code) to provide some sort of seamless
>>migration/alternatives
>>(similar way it has been done in case of libmysql and mysqlnd)?
>>In short - just aliasing the old mysql_* to mysqli_* functions (as most
>>used
>>like _query, _fetch_row/assoc have just mixed variable order)?
>>
>
> Reimplementing ext/mysql inside PHP makes no sense. The result of this wo=
uld be (almost) the exact same code as we have. (ext/mysql is a exremely sm=
all wrapper over libmysql/mysqlnd only special thngs are pconnect, auto con=
nect and reusage of default connection) What one might try to do is changin=
g ext/mysql to not use a resource but an mysqli object, then users might sw=
ich module by module, instead of breaking the application completely. But I=
 fear we will introduce many bugs that way as  this is a quite huge patch. =
An alternative approach might be to reimplement mysql_* functions using PHP=
 userland code based on mysqli. Then users can load that lib (php.ini autop=
repend_file) for compatibility and bugs can be fixed relatively simple  (no=
 C needed, no PHP release needed, ...) but again: writing such a lib is a r=
elatively huge project.
>
> In my opinion we tell users as good as we can that ext/mysql is deprecate=
d for some time, if we really want to get rid of it, we have to add E_DEPRE=
CATED and then remove it.Waiting a year more won't change much, there will =
always people who hit it.

+1 on all of that. I was trying to crystallise my thoughts on the way
home, and you've done it for me. Thanks, Johannes. :)

Adam