Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63929 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44248 invoked from network); 16 Nov 2012 16:20:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Nov 2012 16:20:08 -0000 Authentication-Results: pb1.pair.com smtp.mail=lists@rotorised.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lists@rotorised.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rotorised.com from 117.55.227.24 cause and error) X-PHP-List-Original-Sender: lists@rotorised.com X-Host-Fingerprint: 117.55.227.24 mta24-data1.ironport2.cbr1.mail-filtering.com.au Received: from [117.55.227.24] ([117.55.227.24:55939] helo=mta24-data1.ironport2.cbr1.mail-filtering.com.au) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1C/D5-08060-2B766A05 for ; Fri, 16 Nov 2012 11:20:03 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAGlnplCva78L/2dsb2JhbABEw26CHgEBBWwMARALGAkWDwkDAgECAUUGDQEHAQGICAy+PowzJIRpA5cYhDwTiliDAQ X-IronPort-AV: E=Sophos;i="4.83,265,1352034000"; d="scan'208";a="77308087" Received: from ju001lcs02.dfw.the-server.net.au (HELO ju001lcs02.dfw.the-server.com.au) ([175.107.191.11]) by smtp-data2.ironport2.cbr1.mail-filtering.com.au with ESMTP; 17 Nov 2012 03:19:54 +1100 Received: from [27.33.45.210] (port=55844 helo=[192.168.2.104]) by ju001lcs02.dfw.the-server.com.au with esmtpa (Exim 4.80) (envelope-from ) id 1TZOdz-002oo2-UW; Sat, 17 Nov 2012 03:19:52 +1100 Message-ID: <50A667AE.2000900@rotorised.com> Date: Sat, 17 Nov 2012 02:19:58 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Rasmus Lerdorf CC: Pierre Joye , Philip Olson , Patrick ALLAERT , Anthony Ferrara , Will Fitch , Stas Malyshev , Adam Harvey , Devis Lucato , PHP Developers Mailing List References: <50A2D672.7010600@gmail.com> <50A30144.5070305@phpgangsta.de> <50A3BEC0.8030607@gmail.com> <50A54713.8090102@sugarcrm.com> <50A549EB.2020408@lerdorf.com> <50A5FB0C.1080602@lerdorf.com> <50A5FF83.1060706@lerdorf.com> <50A6088B.5010701@rotorised.com> <50A663EF.3020401@lerdorf.com> In-Reply-To: <50A663EF.3020401@lerdorf.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation From: lists@rotorised.com (Ryan McCue) Rasmus Lerdorf wrote: > On 11/16/2012 01:34 AM, Ryan McCue wrote: >> Pierre Joye wrote: >>> Wordpress lead developer statement is rather clear: Go ahead, we will follow. >> >> Indeed, we have patches written already [1], but they were low priority. >> The plan is to aim for landing these in the next major version, assuming >> PHP does go ahead with this. >> >> [1]: http://core.trac.wordpress.org/ticket/21663 > > So, I am curious, why are you waiting on us for this? Is it because > ext/mysql does everything you need and you simply have no need for any > of the new and obviously better features in mysqli? I would have thought > you would have switched to mysqli years ago if it was available and only > used ext/mysql as a desperation fallback if that was all that was available. I can't speak for all of WordPress' history, but generally, it works well enough. That's one of the reasons addslashes() was used instead of mysql_real_escape_string() for a long time (and can still occur). It's a crucial component, and hence changes to it (especially larger ones) fall under "if it ain't broke, don't fix it". The gains in mysqli/PDO just aren't enough to justify the changes. For example, prepared statements are a large advantage of mysqli/PDO. The problem is, the way database access is done in WordPress means that they couldn't be used in a backwards compatible way (although I think we may be able to fix that). -- Ryan McCue