Cannot disable audit stacktraces

[GoogleCodeExporter]

This is perhaps a cosmetic issue.

In my unit tests (call them integration tests if you want) I will sometimes 
violate database constraints and check whether the expected error is raised. 
Now with log4jdbc this leads to a full stacktrace from the jdbc.audit, 
jdbc.sqlonly and jdbc.sqltiming.

I my case, that’s 3 stacktraces. See issue #49 for why I don’t use FATAL to 
cut this down to only 1. But even a single stacktrace is not helpful in this 
case.

Original issue reported on code.google.com by MichaelPiefel on 29 Mar 2012 at 7:02

[GoogleCodeExporter]

Would you like the error to be reported without the stack trace? -- just the 
exception message?  I could see how that might be useful...

Original comment by [email protected] on 29 Mar 2012 at 11:53

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect