Chris wrote:
That won't tell you where a query comes from ;) Add a debug_backtrace
into the class to also pinpoint where the query was called from.
Complicated queries built on variables (or even just long queries
built over multiple lines) will be hard to find just by looking at the
mysql query log.
I agree with chris and I do the same thing, also with a class or a
wrapper function/s that handle your queries you can also decided on what
databases the query should run, say you have Master-Slave replication
setup with mysql, you could run selects on the slaves and updates/delete
in the master without the class deciding which one it should run on
Clive
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
