Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52115 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30208 invoked from network); 30 Apr 2011 18:47:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Apr 2011 18:47:26 -0000 Authentication-Results: pb1.pair.com smtp.mail=shadda@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=shadda@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: shadda@gmail.com X-Host-Fingerprint: 209.85.160.42 mail-pw0-f42.google.com Received: from [209.85.160.42] ([209.85.160.42:52609] helo=mail-pw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 95/74-10915-D395CBD4 for ; Sat, 30 Apr 2011 14:47:26 -0400 Received: by pwj3 with SMTP id 3so2371774pwj.29 for ; Sat, 30 Apr 2011 11:47:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:mime-version:content-type:subject:date :in-reply-to:to:references:message-id:x-mailer; bh=dSHioSShvnLR+0U/gEGVnLEpvpNnxBeFUn8LRoioZ+w=; b=RPTZnJwIPTdzqFnkPLFFnK1VucCQ2xHqWHASLXMgeoIVEOuK7NEcA6rVgcep0YdHnl JhMM3S/ytx0XnXq1/JQo/KhLA1XQ/pbWAnqWuI/gjweyIQ7Vstpy2tFQ1cfX2iltY5XU evVVhZrxii8LSG6/bJ0+akckN6QtErfUqQqOc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; b=Edo888lqaT6TgHBn5DOTqXQcBfztD5ZMgIGFYoOanPThbq3zUFGGpKejaV6nS5oT39 5E64wQY/bYYsst2wCEakIOJL3eLCnSqMSpi967sqa99j7kmSUYA+VfCnLVPNSwfpanaV fuG9DClsZ2LPpQhsnoU+8njMAJv6b/oqxnofg= Received: by 10.68.68.196 with SMTP id y4mr6678300pbt.427.1304189243210; Sat, 30 Apr 2011 11:47:23 -0700 (PDT) Received: from [192.168.1.100] ([98.156.62.98]) by mx.google.com with ESMTPS id m1sm44790pbb.47.2011.04.30.11.47.20 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Apr 2011 11:47:22 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-15--535478097 Date: Sat, 30 Apr 2011 13:47:16 -0500 In-Reply-To: To: Internals Mailing List References: <4DBC2D1B.10302@lerdorf.com> <4DBC4885.7010209@sugarcrm.com> <4DBC4C9A.2050502@lerdorf.com> Message-ID: <7FC73036-1493-43D5-A593-17B70E05D312@gmail.com> X-Mailer: Apple Mail (2.1084) Subject: Re: [PHP-DEV] Change Request: Make PDO default to not emulate prepared statements for MySQL From: shadda@gmail.com (Matt Wilson) --Apple-Mail-15--535478097 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Actually, I'm talking out my ass. I know it's some version prior to 2005 = and I'm only guessing I meant SP3. I don't work on it, i've just heard = the number 3 thrown around with it. I'll remove myself from the = conversation before I make a larger fool of myself :) On Apr 30, 2011, at 1:44 PM, Ferenc Kovacs wrote: >=20 >=20 > On Sat, Apr 30, 2011 at 8:16 PM, Matt Wilson wrote: > Really would depend on the user. Part of my company still runs on = SQLServer 2003, for instance... >=20 > Corporate infrastructure rarely sees upgrades. Your cousin with the = wordpress fetish, on the other hand... >=20 >=20 > what is SQLServer 2003? > can't see that on http://en.wikipedia.org/wiki/Microsoft_SQL_Server > btw. SQLServer has more enterprise level lifecycle: > http://support.microsoft.com/lifecycle/?p1=3D2852 > http://support.microsoft.com/lifecycle/?p1=3D2852 >=20 > it's much longer than the mysql 2 years after first GA + 3 years = extended support. > = http://www.mysqlperformanceblog.com/2008/08/22/mysql-end-of-life-eol-polic= y/ >=20 > so imo enterprise doesn't mean that you run EOLed version, but that = you have longer support so you can upgrade less frequently. > for example PCI-DSS mandates: > "All critical systems must have the most recently released software = patches to prevent exploitation.=20 > Organizations should apply patches to less-critical systems as soon as = possible, based on a risk-based vulnerability management program." >=20 > I don't see why can't we change this for php-next. > That would still give us time to document the change and for the users = to take actions. > I don't think that many people who uses 5.0 when php-next get released = would be eager to upgrade. >=20 > Tyrael >=20 > Tyrael >=20 --Apple-Mail-15--535478097--