[
https://issues.jboss.org/browse/AS7-1522?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-1522:
-----------------------------------
Class org.hibernate.engine.jdbc.spi.SqlStatementLogger appears to be doing the logging in
Hibernate 4.
This class contains a logger that is based on the above class name, so maybe try
configuring DEBUG for "org.hibernate.engine.jdbc.spi.SqlStatementLogger" instead
of "org.hibernate.SQL"
Regression in Hibernate's logging to find query errors
------------------------------------------------------
Key: AS7-1522
URL:
https://issues.jboss.org/browse/AS7-1522
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.0.0.Final
Environment: Jenkins build 1491
Reporter: Juergen Zimmermann
Assignee: Scott Marlow
Attachments: server.log, standalone.xml, testcase-src.zip, testcase.ear.zip
Hibernate 3.x is logging the generated SQL queries when the logger category
org.hibernate.SQL is set to DEBUG. This feature is extremely helpful in finding mapping
errors because you can inspect the mapping result in the log file. For instance, see the
Hibernate docs at
http://docs.jboss.org/hibernate/core/3.6/reference/en-US/html/session-con...
I'll attach a testcase so that you can easily reproduce this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira