Re: Change Request: Make PDO default to not emulate prepared statements for MySQL
| From: | Ferenc Kovacs | Date: | Sat, 30 Apr 2011 18:44:11 +0000 |
| Subject: | Re: Change Request: Make PDO default to not emulate prepared statements for MySQL | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-52113@lists.php.net to get a copy of this message | ||
On Sat, Apr 30, 2011 at 8:16 PM, Matt Wilson <shadda@gmail.com> wrote:
> Really would depend on the user. Part of my company still runs on SQLServer
> 2003, for instance...
>
> Corporate infrastructure rarely sees upgrades. Your cousin with the
> wordpress fetish, on the other hand...
>
>
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=2852
http://support.microsoft.com/lifecycle/?p1=2852
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-policy/
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.
Organizations should apply patches to less-critical systems as soon as
possible, based on a risk-based vulnerability management program."
<http://www.mysqlperformanceblog.com/2008/08/22/mysql-end-of-life-eol-policy/>
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.
Tyrael
Tyrael