Hello,

I hope I'm not upsetting anyone with this but I thought someone might find it interesting:

I am working on a JDBC Logging tool and I just finished the first release. The objective is to get logging at driver level so you can see exactly what statements are passed to the database. The tool is easy to use and it works fine with hibernate. You can find it on sourceforge:
http://jdbclogger.sourceforge.net/

so what is different about this tool and lets say p6spy or similar ?

well ... not mutch.. :) the main reason would be that p6spy hasn't had a release in quite some time...

ok - but what part of p6 doesn't work and work in jdbclogger?

Well to tell you the truth I haven't used p6spy that mutch..

JDBC Logger was actually started by Martin because he had problems with some bugs in p6spy and nobody was there to fix them.. the comunity is mostly dead. I just tried their bug tracker and the page doesn't even load:
http://bugzilla.irongrid.com/

Another reason for doing this project is that we want something verry simple that needs as little effort as possible to work with.. p6spy isn't too complicated to use but JDBC Logger is even simpler.

ok. cool.