Yea if you're only targeting 1 db, then why not use that class? At
least then there's the php manual to figure out what something does.
Because then to add query logging for the whole app, you just need to put it
in the class :)
(I've done that before to check what's being run and where from, comes in
very handy).
That's done by tail -f /var/log/mysql/query.log. :D
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.
--
Postgresql & php tutorials
http://www.designmagick.com/