Hi, I forgot to mention MySQL's query cache. This change may have negative performance impact, since prepared query is not cached and native prepared query may not be used by other requests.
It would be nice to have an option keeping prepared statement when PDOStatement destroyed. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net 2012/6/20 Yasuo Ohgaki <yohg...@ohgaki.net>: > Hi, > > I'm not opposed to this change, but I would like to give some ideas. > > If I use PDO postgresql and prepared statement, it executes native > prepared query. However, prepared statement is released(removed) > when PDOStatement object is destroyed. > > If PDO MySQL made like this, performance will not increase much > unless app issues the same SQL query over and over during request. > It would be nice to have option for not to release prepared query for > better performance. > > BTW, PDO should have method for setting client/database encoding. > > Regards, > > -- > Yasuo Ohgaki > yohg...@ohgaki.net > > > 2012/6/15 Anthony Ferrara <ircmax...@gmail.com>: >> Hello all, >> >> 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. However, Rasmus did mention that it was a >> possibility for 5.4 ( >> http://marc.info/?l=php-internals&m=130418875017027&w=2 ). Since that >> ship has sailed, I submitted a pull request for trunk to change the >> default value of prepared statement emulation for MySQL. >> >> https://github.com/php/php-src/pull/108 >> >> https://bugs.php.net/bug.php?id=54638 >> >> Does this need to be an RFC (should I draft one)? Or can it just be >> pulled as-is? >> >> Thanks, >> >> Anthony >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
