Re: RFC: ext/mysql deprecation
| From: | Christopher Jones | Date: | Tue, 13 Nov 2012 03:29:53 +0000 |
| Subject: | Re: RFC: ext/mysql deprecation | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63830@lists.php.net to get a copy of this message | ||
On 11/12/2012 07:08 PM, Adam Harvey wrote:
On 13 November 2012 08:44, Christopher Jones <christopher.jones@oracle.com> wrote:Content like this deserves to be in RFCs so voters can quickly judge the impact of proposed changes on end users. Thanks for adding it, ChrisAdam, can you: 1. Add this link to the RFC?:Done and done. I've added a (short) workarounds section towards the bottom, which can be moved up later if the RFC is accepted. Against that, I'm not a big fan of RFCs as documentation, but that's a separate discussion. :)https://wikis.oracle.com/display/mysql/Converting+to+MySQLi2. 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.
Adam-- christopher.jones@oracle.com http://twitter.com/#!/ghrd