It seems that PDO behaviour changes drastically when working with different versions of mysql client library.
We have tried to use only PDO::MYSQL or only mysqli , but that didn’t work well with all kinds of setups.
The most prominent issue we had was multi-statement queries.
On some setups it works smooth with mysqli and on some with PDO.
Also, it looks like mysqli is not ready for named parameters in prepared queries, so the write connection was setup by default to use PDO component.
Also, if you wish to enable buffered query in PDO, uncomment the line # 71 in lib/Varien/Db/Adapter/Pdo/Mysql.php
As you can see we have played with it too…
It seems that PDO behaviour changes drastically when working with different versions of mysql client library.
We have tried to use only PDO::MYSQL or only mysqli , but that didn’t work well with all kinds of setups.
The most prominent issue we had was multi-statement queries.
On some setups it works smooth with mysqli and on some with PDO.
Also, it looks like mysqli is not ready for named parameters in prepared queries, so the write connection was setup by default to use PDO component.
Also, if you wish to enable buffered query in PDO, uncomment the line # 71 in lib/Varien/Db/Adapter/Pdo/Mysql.php
As you can see we have played with it too…
Did everything said here, still no luck. When I replace the dll with the one given here, I get another error as:
Fatal error: Call to a member function children() on a non-object in C:\xampp\htdocs\magento\app\code\core\Mage\Core\Model\Config.php on line 655
Also uncommenting the line 71 in the above lib file had no effect at all.
can we get a bit more info on this new dll file download? kinda surprised that ppl here aren’t a little bit wary that they’re downloading a random file from sites called hackthissite.org and such