Re: [PATCH - PR] Disable ATTR_EMULATE_PREPARES by default for PDO_Mysql

From: Date: Fri, 15 Jun 2012 16:28:50 +0000
Subject: Re: [PATCH - PR] Disable ATTR_EMULATE_PREPARES by default for PDO_Mysql
References: 1 2  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message 



Am 15.06.2012 03:01, schrieb Anthony Ferrara:

I raised this topic on list over a year ago (
http://marc.info/?l=php-internals&m=130417646507744&w=2 ). It was
determined that it wasn't time yet to disable prepared statement
emulation for MySQL yet.



Does this need to be an RFC (should I draft one)? Or can it just be
pulled as-is?


It needs an RFC because it needs to document whether or not the other
DB drivers should also be changed.

On 06/15/2012 08:34 AM, Ulf Wendel wrote:

As long as client-side escaping is done properly, there is no
practical difference between the [client vs server -prepare]
approaches.


The big problem with this line of reasoning is that the client must
know exactly the same dialect of SQL/XQUERY/whatever that the server
does.  Since we can't predict the future, and so a new DB might
introduce some funky syntax, then client preparing could break visibly
or invisibly.  The DB client & DB server code architecture needs to
head to a model where server side prepares work (and are easy etc).

Chris

-- 
[email protected]
http://twitter.com/#!/ghrd

Thread (40 messages)

« previous php.internals (#60847) next »