Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53883 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20826 invoked from network); 11 Jul 2011 17:56:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jul 2011 17:56:43 -0000 X-Host-Fingerprint: 96.2.18.191 host-191-18-2-96.midco.net Date: Mon, 11 Jul 2011 13:56:43 -0400 Received: from [96.2.18.191] ([96.2.18.191:4872] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/F2-30857-A593B1E4 for ; Mon, 11 Jul 2011 13:56:43 -0400 Message-ID: To: internals@lists.php.net References: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org> <4E1B19B7.60703@oracle.com> User-Agent: slrn/pre1.0.0-18 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit X-Posted-By: 96.2.18.191 Subject: Re: [PHP-DEV] deprecating ext/mysql From: weierophinney@php.net (Matthew Weier O'Phinney) On 2011-07-11, Paul Dragoonis wrote: > On Mon, Jul 11, 2011 at 4:41 PM, Christopher Jones > wrote: > > On 7/10/11 10:03 AM, Philip Olson wrote: > > > What this means to ext/mysql: > > > > > >  - Softly deprecate ext/mysql with education (docs) starting today > > >  - Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0 > > >  - Add pdo_mysql examples within the ext/mysql docs that mimic the current > > >    examples, but occasionally introduce features like prepared statements > > >  - Focus energy on cleaning up the pdo_mysql and mysqli documentation > > >  - Create a general "The MySQL situation" document that explains the > > > situation > > > > +1, though check with the MySQL folk about whether they want mysqli or > > pdo_mysql to > > be the recommended path. > > > > Chris > > Yes, +1 from me too. I do indeed think we need to make this a smooth > transition over time. Possibly triggering an E_DEPRECATED for all > ext/mysql usage. Just like the introduction of E_DEPRECATED for 5.3 > functions, we could apply the same approach here. After 5.4 is > released we can put big "Deprecated Warning" notifications on all > php.net/mysql_* functions too. I think we all want this, but to be > realistic from a production point of view, many sites will still be > using ext/mysql. And, to my reading, this is exactly the path that was recommended. The point is to start a "soft" deprecation now via the manual, indicating that users should migrate to other solutions, while simultaneously detailing how to do equivalent operations via ext/mysqli or pdo_mysql. Actual deprecation would happen later. -- Matthew Weier O'Phinney Project Lead | matthew@zend.com Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc