Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60847
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain oracle.com designates 141.146.126.227 as permitted sender)
Message-ID: <4FDB62C2.6090702@oracle.com>
Date: Fri, 15 Jun 2012 09:28:50 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAAyV7nFciZcsL+AW9W4GbhM+PhM3RhWOJ7G0iBQsEHfSWO2QmA@mail.gmail.com> <4FDB5604.5000704@oracle.com>
In-Reply-To: <4FDB5604.5000704@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PATCH - PR] Disable ATTR_EMULATE_PREPARES by default
 for PDO_Mysql
From: christopher.jones@oracle.com (Christopher Jones)



> 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

-- 
christopher.jones@oracle.com
http://twitter.com/#!/ghrd