Logging information

[croffler]

We have a complex system with many data sets. When there is an error in one of the data sets we get this exception:
com.ninja_squad.dbsetup.DbSetupRuntimeException: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
it is difficult to find the actual problem. As far as I can tell, there is no logging in DbSetup.
Would be nice to have some more information

[jnizet]

@croffler Yes, I didn't want to impose a logging framework once again, and wanted to be dependency-free. I agree exceptions can sometimes be cryptic, and I'll maybe try to add some logging mechanism.

In the meantime, can't you find the root cause based on the exception stack trace, or using your debugger?

[croffler]

Makes sense as far as the dependency-free. We are able to debug it and find eventually the problems .... but a little help with logging I think would be great, when you have over a hundred data sets :) BTW DbSetup is really cool , keep up the good work Chris

…

On Wed, Jan 11, 2017 at 10:26 AM, JB Nizet ***@***.***> wrote: @croffler <https://github.com/croffler> Yes, I didn't want to impose a logging framework once again, and wanted to be dependency-free. I agree exceptions can sometimes be cryptic, and I'll maybe try to add some logging mechanism. In the meantime, can't you find the root cause based on the exception stack trace, or using your debugger? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEFNKE3STfW0zBA7I48jNn0AbvYENOcPks5rRJIpgaJpZM4LfMAx> .

[softdays]

+1, it should be very helpful to trace sql query
look at slf4j that's what it's meant for

[gnostrenoff]

+1, logging would be welcome :)

[jkttt]

+1 for logging

[raderio]

+1 for logging
have you checked SLF4J?