Closed GoogleCodeExporter closed 9 years ago
This is a known bug inherited from the original log4jdbc library. The original
developer stated: "the whole idea of filtering on the type of SQL probably was
a bad idea as it's very hard to do that reliably when the SQL gets complex."
See https://code.google.com/p/log4jdbc/issues/detail?id=45
Your problem was also reported in the original library:
https://code.google.com/p/log4jdbc/issues/detail?id=39
If you can think of an effective way to perform the filtering, I'll be glad to
implement it. Otherwise, this will be a "won't fix" :/
Original comment by frederic...@gmail.com
on 4 Jun 2014 at 12:05
Original comment by frederic...@gmail.com
on 24 Jul 2014 at 11:04
Original issue reported on code.google.com by
jst...@tnsi.com
on 28 May 2014 at 5:12Attachments: