On 2011-07-11, Paul Dragoonis <dragoo...@gmail.com> wrote: > On Mon, Jul 11, 2011 at 4:41 PM, Christopher Jones > <christopher.jo...@oracle.com> 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 | matt...@zend.com Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
