From ef27013bab8ce027cce1c3efe4acafb8aef9d2e3 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Fri, 19 Sep 2014 14:35:46 +0200 Subject: Add stderr_full_tracer that additionally traces statement preparation --- doc/manual.xhtml | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) (limited to 'doc/manual.xhtml') diff --git a/doc/manual.xhtml b/doc/manual.xhtml index 6a12f57..13203f0 100644 --- a/doc/manual.xhtml +++ b/doc/manual.xhtml @@ -4139,9 +4139,16 @@ t.commit ();

The odb::tracer class defines a callback interface that can be used to create custom tracer implementations. The - odb::stderr_tracer is a built-in tracer implementation - provided by the ODB runtime. It prints each executed SQL statement - to the standard error stream.

+ odb::stderr_tracer and odb::stderr_full_tracer + are built-in tracer implementations provided by the ODB runtime. + They both print SQL statements being executed to the standard error + stream. The full tracer, in addition to tracing statement executions, + also traces their preparations and deallocations. One situation where + the full tracer can be particularly useful is if a statement (for + example a custom query) contains a syntax error. In this case the + error will be detected during preparation and, as a result, the + statement will never be executed. The only way to see such a statement + is by using the full tracing.

The odb::tracer class is defined in the <odb/tracer.hxx> header file which you will need to -- cgit v1.1