the problem is that some of this might not be part of an api we would like to expose in a public extension point.

still I would consider looking at a patch that provides such an extension point just to know how much/little we need to disclose - so feel free to look into it.

Hello Gavin,

you can make the code working with Spring if you cast the SessionFactory to the interface SessionFactoryImplementor instead of SessionFactoryImpl. (Casting to an interface is slightly better in terms of stability).

Can you please post your latest version of your code that handles NativeSQL as well?

Thanks in advance,
Georg

Hi,

Having the same issue integrating the previously posted code with Spring, the bind parameters simply would not appear in the logs.

After a lot of searching I stumbled across this article:

http://java.sys-con.com/read/204723.htm

Which describes a small package that wraps your JDBC connection and traces out the query and parameters at the debug level.
Here is an example of the output:


By default it will print the code on one line, but a small change to call the Formatter class in hibernate will return the formatting above.

Good luck and thanks for helping my along my search.

You can also do this using Proxool.

Just configure Proxool as your JDBC driver (the same way you do for P6Spy) then switch on statement tracing(*) .

It actually works even better for me than P6Spy because:
* It's not a dead project like P6Spy
* It uses the default Log4J hierarchy and configuration mechanisms (P6Spy is usually awkward to integrate with the rest of your logging strategy)

It might not be as good as P6Spy for your own situation though because I'm not sure how well Proxool operates as a datasource inside an application server. But I only need it during my development testing, so it works well for me.


(*) I found configuring Hibernate with Proxool to be astonishingly painful (I found the same thing when I was using it with Hibernate a couple of years ago too - so no progress there). It's kind of cool once you get it working, but getting it to that point hurts (not just telling hibernate to use proxool and then telling proxool about my JDBC driver, but also being able to configure statement tracing to actually be switched on).

I found this page very helpful: http://hibernate.org/222.html

Hello,

Someone mentioned posting the QueryLogger class on the wiki. Can someone please post a link to the wiki article?

Thank you.

PS: I'm trying figure out how to use the QueryLogger class. I'm new to hibernate. I am saving an object by calling hibernateTemplate.save(<someObject>). I just wan to the SQL that is being executed on the database in a regular SQL format with the values in place so that I can copy them and create an import.sql script.