Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63860
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
Message-ID: <50A2D672.7010600@gmail.com>
Date: Wed, 14 Nov 2012 00:23:30 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: Anthony Ferrara <ircmaxell@gmail.com>
CC: PHP internals <internals@lists.php.net>
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>
In-Reply-To: <CAAyV7nFOGa7UVALSQyAs-A+R0kuEmXoHPrxvCXNBnzAxLy0dww@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

I see several problems with deprecating ext/mysql:

- The extension is not broken. The problem is the bad usage.
It can be used safely, and good developers have been doing
so for ages, by creating php wrappers.
In magic quotes, the work has been the opposite. The developers
had been detecting the feature in php and *disabling* it.

- How many hosts/ISPs have mysqli installed?
I don't have actual numbers, but it used to be much less common
than ext/mysql, which means that unless they those customers
won't be able to run the applications forced to migrate to mysqli.

Yes, the customers should complain and get the extension enabled,
but what will happen instead is that they will use outdated version X
of WordPress, since that one works.

So the problem really moves onto the CMS providers, do they support
new php versions and drop customers in shared hosting, do they delay
supporting the new php versions, or do they reimplement mysql_*
in php?

- A "magic porting script" has been mentioned on this thread.
It is not on the docs, so it is really as if it didn't exist for the 99%
of the
population. Moreover, there is even a FAQ stating that there are no
migration
scripts right now:
http://php.net/manual/en/faq.databases.php#faq.databases.mysql.deprecated

It should be linked from every mysql page.


- If you are sure your ext/mysql usage is safe, it is not possible to
disable the warning
for this functions but keep the other E_DEPRECATED.


- I'm quite sure that there will be a number of problems where the
replacements have
issues, but they are unlikely to be fixed if not forced. For instance, I
remember a
php script using mysql that from reading the code, it shouldn't be
working but it
somehow did. Completely unmaintained, of course.