Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63826
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain oracle.com designates 141.146.126.69 as permitted sender)
Message-ID: <50A197D2.5070307@oracle.com>
Date: Mon, 12 Nov 2012 16:44:02 -0800
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Adam Harvey <aharvey@php.net>
CC: PHP internals <internals@lists.php.net>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
In-Reply-To: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: christopher.jones@oracle.com (Christopher Jones)



On 11/12/2012 05:00 AM, Adam Harvey wrote:
> Hi everyone,
>
> I've written an RFC to cover deprecating ext/mysql in PHP 5.5:
> https://wiki.php.net/rfc/mysql_deprecation. While we handled the soft
> deprecation in the documentation purely via a straw poll on Internals,
> I presume this will end up needing to go to a vote, hence the RFC.
>
> I won't rehash the background overly (there's some more detail in the
> RFC), other than to note that we've now had deprecation notices on all
> mysql_* functions in the manual for about six months and that the
> logical next step is to start generating E_DEPRECATED notices when
> users connect via mysql_connect(), mysql_pconnect() or the implicit
> ext/mysql connection routines. It's my belief that doing so will
> hasten the move of users to the more modern (and supported) APIs
> available: mysqli and PDO, and that this process will also likely
> encourage some users to switch to safer patterns such as prepared
> queries at the same time.
>
> I must apologise for the lateness of this RFC: I had hoped to do this
> some time before alpha 1, but travel and illness have taken their
> toll. Better late than never!
>
> So, please provide comments, feedback, concerns, and so on. Obviously,
> this isn't going to a vote for at least a couple of weeks, but earlier
> feedback is better.
>
> Thanks,
>
> Adam
>

I'm +1 on using E_DEPRECATED.  Anything beyond that would be -1 since
it is likely to break BC (I note that the Release Process RFC doesn't
defines "compatibility", but I think we are have a gut feel for what
it means)

Adam, can you:

   1. Add this link to the RFC?:
      https://wikis.oracle.com/display/mysql/Converting+to+MySQLi

   2. Mention how to turn off E_DEPRECATED warnings in the RFC?

When users of 5.5 stumble on the new messages, we can then simply
point them to the RFC.

Chris

-- 
christopher.jones@oracle.com
http://twitter.com/#!/ghrd