From dfba83f1ef3b5856d36dc29da0b6e02f51bc36b3 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 9 Nov 2011 14:15:00 +0200 Subject: Proofreading fixes to tracing support documentation --- doc/manual.xhtml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/manual.xhtml b/doc/manual.xhtml index 110a39d..6706322 100644 --- a/doc/manual.xhtml +++ b/doc/manual.xhtml @@ -1509,7 +1509,7 @@ INSERT INTO `person` (`id`,`first`,`last`,`age`) VALUES (?,?,?,?)

Note that we see question marks instead of the actual values because ODB uses prepared statements and sends the data to the - database in binary form. For more information on tracing refer + database in binary form. For more information on tracing, refer to Section 3.12, "Tracing SQL Statement Execution". In the next section we will see how to access persistent objects from our application.

@@ -3273,7 +3273,7 @@ t.commit ();

3.12 Tracing SQL Statement Execution

-

Oftentimes it is useful to understand what SQL statement are +

Oftentimes it is useful to understand what SQL statements are executed as a result of high-level database operations. For example, we can use this information to figure out why certain transactions don't produce desired results or why they take @@ -3323,7 +3323,7 @@ t.commit ();

The first two tracer() functions allow us to set the tracer object with the second one allowing us to clear the current tracer by passing a NULL pointer. The - last tracer() function allow us to get the + last tracer() function allows us to get the current tracer object. It returns a NULL pointer if there is no tracer in effect. Note that the tracing API does not manage the lifetime of the tracer object. The tracer @@ -3374,7 +3374,7 @@ namespace odb functions do nothing while the first execute() function calls the second one passing the statement text as the second argument. As a result, if all you are interested in are the - SQL statements being executed, that you only need to override the + SQL statements being executed, then you only need to override the second execute() function.

In addition to the common odb::tracer interface, @@ -3387,7 +3387,7 @@ namespace odb

As an example, consider a more elaborate, PostgreSQL-specific tracer implementation. Here we rely on the fact that the PostgreSQL - ODB runtime uses names to identify prepared statement and this + ODB runtime uses names to identify prepared statements and this information can be obtained from the odb::pgsql::statement object:

-- cgit v1.1