> On Mar 31, 2016, at 1:50 AM, Aristedes Maniatis <a...@maniatis.org> wrote:
>
> Should we change most of CommonsJdbcEventLogger to DEBUG? For some reason the
> whole thing is bound to INFO?
>
> @Override
> public boolean isLoggable() {
> return logger.isInfoEnabled();
> }
>
>
> logQueryError() should be ERROR or at least WARN. Pretty much everything else
> should be DEBUG.
Cayenne has always logged SQL at INFO level. And I'd like to have it on by
default. Turning it off for Jenkins (or your own apps) is not a problem -
logger levels are configurable. I am not doing it for other reasons:
1. We often want SQL to be logged during tests for tracing purposes.
2. I am not yet convinced Cayenne logs are the culprit here. Consider that
these builds are done with an empty local Maven repo, so Maven downloads a
bunch of dependencies. Take a look at raw logs on Travis. It is not yet clear
SQL logs are the majority.
So I'd like to play with it a bit, and see what we can trim without sacrificing
clarity. Long logger names and timestamps are the first candidates.
Andrus
