The following comment has been added to this issue:
Author: John Kristian
Created: Thu, 30 Oct 2003 5:54 PM
Body:
Yes, but at DEBUG level, and via the same log4j category as many other messages of more limited interest. The people who will support my Hibernate-based application strongly prefer to enable/disable SQL tracing independent of all the other messages logged via BatcherImpl.log. I imagine many others will, too.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-438
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-438
Summary: Log SQL
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Kristian
Created: Thu, 30 Oct 2003 2:52 PM
Updated: Thu, 30 Oct 2003 2:52 PM
Description:
Please log executed SQL, in addition to (or instead of) passing it to System.out.println. System.out is useful for development. But logging is often better in a production server; for example, when System.out is directed to /dev/null.
The patch logSql.diff-u (attached) works for me.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
