Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52124
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        b=XUTwBjlpeLhPXKjItNgoGqASYNcbOVJCCQ7jJucVQyQQCGeK3NpwARG92J4pzXdjqs
         N9xP7yPaReO3fDQuj3S1jqzHWbi1qq7N92bsfpyk+HxV2NFHSfzSEgNcm5wJNosqPipf
         de9clqRKOXm/kYE++thtsT8DryEKWQZbTnEHQ=
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <1304193525-sup-1492@fewbar.com>
References: <BANLkTimtRdY_+Jj46jFEqkseuz7WD1ZPZQ@mail.gmail.com>
	<4DBC2D1B.10302@lerdorf.com>
	<4DBC4885.7010209@sugarcrm.com>
	<4DBC4C9A.2050502@lerdorf.com>
	<1304193525-sup-1492@fewbar.com>
Date: Sat, 30 Apr 2011 23:26:57 +0200
Message-ID: <BANLkTin1D7-NxVTva2=pouB3Mf50z7t2kA@mail.gmail.com>
To: Clint Byrum <clint@ubuntu.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=0016364c704640579e04a229735c
Subject: Re: [PHP-DEV] Change Request: Make PDO default to not emulate
 prepared statements for MySQL
From: info@tyrael.hu (Ferenc Kovacs)

--0016364c704640579e04a229735c
Content-Type: text/plain; charset=UTF-8

On Sat, Apr 30, 2011 at 10:05 PM, Clint Byrum <clint@ubuntu.com> wrote:

> Excerpts from Rasmus Lerdorf's message of Sat Apr 30 10:53:30 -0700 2011:
> > On 04/30/2011 10:36 AM, Stas Malyshev wrote:
> > > Hi!
> > >
> > >> Do you realize why we did this in the first place? The common versions
> > >> of MySQL in use out there are not very clever when it comes to the
> > >> native prepared statement handling. First, there is no prepared
> > >> statement cache, so there is no benefit to doing them natively, but
> > >
> > > Since 5.1.17 there is:
> > > http://dev.mysql.com/doc/refman/5.1/en/query-cache-operation.html
> > > And 5.1.17 is 4 years old already.
> >
> > People upgrade their databases even slower than they upgrade their PHP.
>
> That said, MySQL 5.0 is only in "Extended Support"[1] (read: security
> only) from Oracle, and will likely be deprecated to full EOL at some
> point in the near future. I think its fair to say that if something is
> a massive problem for a version that the authors don't even support,
> its probably ok to leave those users behind with defaults, as long as
> you give them a way to turn it off. So maybe this could be considered
> blocked only by 5.0's EOL.
>
> --
> [1] http://www.mysql.com/support/eol-notice.html
>
>
if oracle keeps the original lifecycle of the mysql product line, then the 2
year extended support is 2 years from the eol of the active support, so it
means that 5.0 extended will end 2011 dec 31.
but the extended support is only available for those who bought the premium
support, so for the rest of us, 5.0 is already EOL

Tyrael

--0016364c704640579e04a229735c--