On 03/09/15 12:25, Ferenc Kovacs wrote: >> Last time we discussed this it was Anthony who proposed the change and >> > Rasmus shed some light on why did we have the emulation in the first place. >> > We can have change the default but we should have an RFC clearly stating >> > the impact (an additional network roundtrip and the native prepares being >> > less flexible vs. better security and performance gain in case of executing >> > the same prepared query multiple times) >> > > for the record, here is the last discussion on the topic: > http://grokbase.com/t/php/php-internals/126fcmvv04/patch-pr-disable-attr-emulate-prepares-by-default-for-pdo-mysql
And the information on just how each database handles the various abstractions of place holders is still missing. While the current proposal is framed as only effecting the pdo_mysql driver, if the default way this is handled then affects what IS currently working cross-database then it does have a much wider impact? That PDO is simply not up to the job it was originally pushed to provide is a fact and making it work just for one database begs the question "why keep it". Testing with a generic set of code should work identically across all supported databases and that does mean that some level of emulation is required but currently there is no documentation on just what does and what does not work. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
