Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53871 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80224 invoked from network); 11 Jul 2011 14:28:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jul 2011 14:28:01 -0000 X-Host-Fingerprint: 96.2.18.191 host-191-18-2-96.midco.net Date: Mon, 11 Jul 2011 10:28:00 -0400 Received: from [96.2.18.191] ([96.2.18.191:29099] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CF/90-09103-F680B1E4 for ; Mon, 11 Jul 2011 10:28:00 -0400 Message-ID: To: internals@lists.php.net References: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org> User-Agent: slrn/pre1.0.0-18 (Linux) X-Posted-By: 96.2.18.191 Subject: Re: deprecating ext/mysql From: weierophinney@php.net (Matthew Weier O'Phinney) On 2011-07-10, Philip Olson wrote: > Greetings PHP geeks, > > Don't panic! This is not a proposal to add errors or remove this > popular extension. Not yet anyway, because it's too popular to do that > now. > > The documentation team is discussing the database security situation, > and educating users to move away from the commonly used ext/mysql > extension is part of this. > > This proposal only deals with education, and requests permission to > officially convince people to stop using this old extension. This > means: > > - Add notes that refer to it as deprecated > - Recommend and link alternatives > - Include examples of alternatives > > There are two alternative extensions: pdo_mysql and mysqli, with PDO > being the PHP way and main focus of future endeavors. Right? Please > don't digress into the PDO v2 fiasco here. > > 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 > > The PHP community has been recommending alternatives for several years > now, so hopefully this won't be a new concept or shock to most users. Big +1 from me. We actually chose not to do a Mysql adapter in Zend_Db primarily due to the security issues, but also due to the much more advanced feature sets available in the mysqli and pdo/mysql adapters. -- 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