diff --git a/openjpa-project/src/doc/manual/ref_guide_logging.xml b/openjpa-project/src/doc/manual/ref_guide_logging.xml index b987cbf16..90beaf57f 100644 --- a/openjpa-project/src/doc/manual/ref_guide_logging.xml +++ b/openjpa-project/src/doc/manual/ref_guide_logging.xml @@ -204,6 +204,29 @@ Pretty-printing properties configuration might look like so: value="PrettyPrint=true, PrettyPrintLineLength=72"/> + + + + + SQLDiag + + + log messages + + +openjpa.jdbc.SQLDiag: This logging channel provides additional +information about entity actitvies such as create, find, update or delete, and eager +loading of relation or field properties. If you enable this channel, it is recommanded +that openjpa.jdbc.SQL channel is also enabled. +The additional trace can help you relate the entity activities to the execution of +SQL statements that OpenJPA issued to the datastore. + + +When using the built-in OpenJPA logging facilities, you can enable SQLDiag logging +by adding SQLDiag=TRACE to your openjpa.Log +property. + + @@ -367,6 +390,7 @@ log4j.category.openjpa.MetaData=WARN log4j.category.openjpa.Enhance=WARN log4j.category.openjpa.Query=WARN log4j.category.openjpa.jdbc.SQL=WARN +log4j.category.openjpa.jdbc.SQLDiag=WARN log4j.category.openjpa.jdbc.JDBC=WARN log4j.category.openjpa.jdbc.Schema=WARN @@ -462,6 +486,7 @@ openjpa.MetaData.level=INFO openjpa.Enhance.level=INFO openjpa.Query.level=INFO openjpa.jdbc.SQL.level=INFO +openjpa.jdbc.SQLDiag.level=INFO openjpa.jdbc.JDBC.level=INFO openjpa.jdbc.Schema.level=INFO