Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From <a href="http://docs.jboss.org/hibernate/core/3.3/reference/en/html/session-configuration.html#configuration-logging" rel="noreferrer">http://docs.jboss.org/hibernate/core/3.3/reference/en/html/session-configuration.html#configuration-logging</a></p> <p>Here's the list of logger categories:</p> <pre><code>Category Function org.hibernate.SQL Log all SQL DML statements as they are executed org.hibernate.type Log all JDBC parameters org.hibernate.tool.hbm2ddl Log all SQL DDL statements as they are executed org.hibernate.pretty Log the state of all entities (max 20 entities) associated with the session at flush time org.hibernate.cache Log all second-level cache activity org.hibernate.transaction Log transaction related activity org.hibernate.jdbc Log all JDBC resource acquisition org.hibernate.hql.ast.AST Log HQL and SQL ASTs during query parsing org.hibernate.secure Log all JAAS authorization requests org.hibernate Log everything (a lot of information, but very useful for troubleshooting) </code></pre> <p>Formatted for pasting into a log4j XML configuration file:</p> <pre><code>&lt;!-- Log all SQL DML statements as they are executed --&gt; &lt;Logger name="org.hibernate.SQL" level="debug" /&gt; &lt;!-- Log all JDBC parameters --&gt; &lt;Logger name="org.hibernate.type" level="debug" /&gt; &lt;!-- Log all SQL DDL statements as they are executed --&gt; &lt;Logger name="org.hibernate.tool.hbm2ddl" level="debug" /&gt; &lt;!-- Log the state of all entities (max 20 entities) associated with the session at flush time --&gt; &lt;Logger name="org.hibernate.pretty" level="debug" /&gt; &lt;!-- Log all second-level cache activity --&gt; &lt;Logger name="org.hibernate.cache" level="debug" /&gt; &lt;!-- Log transaction related activity --&gt; &lt;Logger name="org.hibernate.transaction" level="debug" /&gt; &lt;!-- Log all JDBC resource acquisition --&gt; &lt;Logger name="org.hibernate.jdbc" level="debug" /&gt; &lt;!-- Log HQL and SQL ASTs during query parsing --&gt; &lt;Logger name="org.hibernate.hql.ast.AST" level="debug" /&gt; &lt;!-- Log all JAAS authorization requests --&gt; &lt;Logger name="org.hibernate.secure" level="debug" /&gt; &lt;!-- Log everything (a lot of information, but very useful for troubleshooting) --&gt; &lt;Logger name="org.hibernate" level="debug" /&gt; </code></pre> <p>NB: Most of the loggers use the DEBUG level, however org.hibernate.type uses TRACE. In previous versions of Hibernate org.hibernate.type also used DEBUG, but as of Hibernate 3 you must set the level to TRACE (or ALL) in order to see the JDBC parameter binding logging.</p> <p>And a category is specified as such:</p> <pre><code>&lt;logger name="org.hibernate"&gt; &lt;level value="ALL" /&gt; &lt;appender-ref ref="FILE"/&gt; &lt;/logger&gt; </code></pre> <p>It must be placed before the root element.</p>
    singulars
    1. This table or related slice is empty.
    1. POConfiguring Hibernate logging using Log4j XML config file?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDave Jarvis
    1. USLoki
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POConfiguring Hibernate logging using Log4j XML config file?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI am not sure what <appender-ref> is doing there, when I change it to an appender in my config, hibernate still seems to log to both console and my file appender. Strange.
      singulars
      1. PO
      1. USJames McMahon
    2. COThis is odd, in Hibernate 3.2.6 for org.hibernate.type you can use DEBUG level and it logs all the parameters. In hibernate 3.5.6 DEBUG is not enough, you have to put TRACE, which is IMHO ok (once you know it) since it really logs a lot!
      singulars
      1. PO
      1. USRiccardo Cossu
    3. COThe class name was refactored on Hibernate 4.2 so for transactions logging you have to use `org.hibernate.engine.transaction`. See: http://docs.jboss.org/hibernate/orm/4.2/devguide/en-US/html/ch02.html#d5e545
      singulars
      1. PO
      1. USgerrytan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload