profiler is nice, but it lacks certain information. Using my custom adapter i'm also able to log auto_increment IDs, how many rows were affected after executing delete/update queries, etc. I find this to be very useful information, especially when trying to debug issues on a production machine where al you have is the information in log files.
I'm still stuck with the problem btw. Where all queries in ZF1 were in the end executed in Zend\Db\Adapter\Pdo\Mysql::query() (which was easily substituted for a custom version as explained in my original post), it seems this is now much deeper nested in the ZF code and not so easily overriden. Am i correct that this can now only be done by somehow forcing a custom version of Zend\Db\Adapter\Driver\Pdo\Statement? So, my question still stands: What is the easiest way to gain control over the part where the query is executed? And preferably the actual query, not the prepared statement. -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/ZF2-How-to-use-custom-db-adpater-How-to-log-database-queries-tp4659302p4659312.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
