I know that I can enable sql logging (using show_sql=true), but is there a way to get better instrumentation. For example, include the following in the log:

- log the sql and the hsql (with the named parameters)
- log the parameters bound to the statement
- log the time taken to execute the sql
- control the format of the log
- determine if the sql should be logged

It would be nice to have an interceptor that I could register that can manage the logging of all sql (loader, persister, native, named-query, generator, etc)

I have looked at the Batcher class, but I do not think it is in the right spot.

Thanks
Gavin

- enable org.hibernate.type debug log
- write a custom log4j appender
- use p6spy or similar

It's true that you can get the bind variables via writing a log4j buffered appender - but that is some work, it's not simple and easy to do.
And p6spy seems not to make your own interceptor possible.

I used the appender for tracing of sql and bind variables after jdbc exceptions in a production environment.
I have seen that the new Interceptor has a method onPreparedStatement which gives you the sql.

Is it planned to give it another method exposing the bind variables, too?