Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53799 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44171 invoked from network); 10 Jul 2011 17:03:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jul 2011 17:03:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=philip@roshambo.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=philip@roshambo.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain roshambo.org from 74.125.83.170 cause and error) X-PHP-List-Original-Sender: philip@roshambo.org X-Host-Fingerprint: 74.125.83.170 mail-pv0-f170.google.com Received: from [74.125.83.170] ([74.125.83.170:44364] helo=mail-pv0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BC/B0-38647-E6BD91E4 for ; Sun, 10 Jul 2011 13:03:44 -0400 Received: by pvh10 with SMTP id 10so2338132pvh.29 for ; Sun, 10 Jul 2011 10:03:39 -0700 (PDT) Received: by 10.68.22.195 with SMTP id g3mr6117937pbf.529.1310317419253; Sun, 10 Jul 2011 10:03:39 -0700 (PDT) Received: from [192.168.1.11] (c-174-61-179-13.hsd1.wa.comcast.net [174.61.179.13]) by mx.google.com with ESMTPS id i9sm7856113pbk.20.2011.07.10.10.03.38 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Jul 2011 10:03:38 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 10 Jul 2011 10:03:36 -0700 Message-ID: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org> To: PHP Developers Mailing List Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: deprecating ext/mysql From: philip@roshambo.org (Philip Olson) 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=20 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. Regards, Philip