Just SQL Logging?

[mmichalek]

Is it possible to configure log4jdbc to log SQL statements, but NOT to
log exceptions? Thanks.

[Arthur Blake]

Because log4jdbc logs the exceptions at ERROR level but it logs the
SQL at INFO level you ought to be able to accomplish that easily with
an appropriate filtering mechanism in your logger of choice.

[mmichalek]

Thanks for the quick response. Is it possible to supply a custom
SpyLogDelegator? If not, what do you think about that idea? It
seems like that would give users of the framework a lot of flexibility
in how things get logged.

Thanks,
Mark

On Mar 12, 2:16 pm, Arthur Blake <arthur.bl...@gmail.com> wrote:
> Because log4jdbc logs the exceptions at ERROR level but it logs the
> SQL at INFO level you ought to be able to accomplish that easily with
> an appropriate filtering mechanism in your logger of choice.
>

[Arthur Blake]

Yes, I have been thinking about that and I agree that it would
definitely add a lot of flexibility. I will probably add that soon
(maybe in the next alpha release.) I'm just not sure of the best way
to expose that. It could be as simple as adding a setter method to
SpyLogFactory to replace the default one... or maybe a system property
so it could be set externally... (or both?) Also thought it might be
nice to have an Observer/Observable pattern so that more than one
SpyLogDelegator could be active at once... but that might be
overkill. Suggestions are welcome.

[mmichalek]

I think that makes a lot of sense. Some people will like the system
property option, and I like setting it on the factory.

[mmichalek]

I submitted a SpyLogFactory that opens things up a bit here:
http://code.google.com/p/log4jdbc/issues/detail?id=5&q=label:Type-Defect