We have a requirement that all database selects must be logged and cannot see any obvious method for achieving this. The onLoad() interceptor method appears to log object loads but not reads of individual columns from HQL queries.

If anyone has successfully implemented a method of doing this perhaps by logging the sql itself or by some other method I would be very grateful for any pointers as to how to go about it.

Thanks.

Why not using the features of your JDBC driver ? Many driver can log everything they do.

If yours doesn't do it, then try P6Spy...

Another approach is to raise Hibernate's debug level and set the showSql property to true.

when you say log, what do you mean by it. Log to a database, log to a file? log where?

If you need to log it to a file, show_sql=true will log your sql's to console. Otherwise I would dig up the code and see when and how the above mentioned log statements gnerated. After that my guess AOP will provide the fastes and least intrusive solution.

HTH,
Alex.

It doesn't log to the console. Hibernate logs to the place you configured, using either Log4j or JDK 1.4 logging. We even have a LogAppender (somewhere on the Wiki) that logs to a database, write your own to log your SQL in whatever way you need.

Make sure you log to a file. Logging all selects to a database
can quicly limit your ability to scale and handle a large load.

Actually, even logging to a file will harm performance. For a local database, I imagine that a write to disk is slower than querying from the database's cache.

Many thanks to all who replied. I am going to investigate P6Spy further as a first step.

Thankyou.

asynchronous flush with file logging, can be a good way of improvement in this case.