Re^3: Can DBI modify queries on the fly?

in reply to Re^2: Can DBI modify queries on the fly?
in thread Can DBI modify queries on the fly?

Understood. I would advise strongly against doing this in production though. Most DBMSs will have a performance penalty for writing to the errorlog (or any external file). But... it's your code/server.

Jason L. Froebe

Blog, Tech Blog

Comment on Re^3: Can DBI modify queries on the fly?

Replies are listed 'Best First'.
Re^4: Can DBI modify queries on the fly? by kyle (Abbot) on Feb 18, 2009 at 03:08 UTC
We're not planning to write everything to a log, but there's a "slow queries" log for when something takes too long, and I'd like those entries to have a little more information in them. Unfortunately, I can't always tell ahead of time which queries those will be, so I need to add my special bonus info to everything.	[reply]
Re^5: Can DBI modify queries on the fly? by jfroebe (Parson) on Feb 18, 2009 at 03:52 UTC
Instead of writing to the DBMS errorlog, how about writing to a table? It would probably have a smaller performance impact. It would also allow you to determine which queries are most often used.. allowing you to focus your energy on the worst. Which DBMS are you using? There might be tools that would identify the slow queries that you could use in conjunction with your code line => query. Jason L. Froebe Blog, Tech Blog	[reply]

In Section Seekers of Perl Wisdom