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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
