Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52123
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fewbar.com from 65.98.207.160 cause and error)
Content-Type: text/plain; charset=UTF-8
To: internals <internals@lists.php.net>
In-reply-to: <4DBC4C9A.2050502@lerdorf.com>
References: <BANLkTimtRdY_+Jj46jFEqkseuz7WD1ZPZQ@mail.gmail.com> <4DBC2D1B.10302@lerdorf.com> <4DBC4885.7010209@sugarcrm.com> <4DBC4C9A.2050502@lerdorf.com>
Date: Sat, 30 Apr 2011 13:05:31 -0700
Message-ID: <1304193525-sup-1492@fewbar.com>
User-Agent: Sup/0.11
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Change Request: Make PDO default to not emulate prepared statements for MySQL
From: clint@ubuntu.com (Clint Byrum)

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