Currently the sqltiming logger has properties that set thresholds for logging
slow SQL statements at the WARN and ERROR levels. It also logs at the ERROR
level any SQL that causes an exception, along with the stack trace.
It would be nice to have a way not to log the exceptions and corresponding SQL
to allow generating just a log of slow SQL to be used for analyzing performance.
It could be another property that controls the behavior of the sqltiming
logger. The sqltiming logger and the sqlonly logger could always log to
different files if someone wanted to separately track slow SQL without loosing
the ability to track down exceptions.
Original issue reported on code.google.com by dtar...@gmail.com on 18 Aug 2010 at 6:06
Original issue reported on code.google.com by
dtar...@gmail.com
on 18 Aug 2010 at 6:06