PostgreSQL 7.2.1 Documentation

Chapter 1. libpq - C Library
1.3. Command Execution Functions
1.3.3. Escaping binary strings for inclusion in SQL queries

I found the line
"The result string length does not include the terminating zero byte of the result."
is not right.
The result string length does indeed include the terminating zero byte.

Christoph Haller

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index f1cb03f887155a6b3713aa1054bfd9ef0b6d0c0c..ca2d7e45e1b0d7a1f2372e1ec43780b33760f9e2 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.91 2002/08/15 02:56:19 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.92 2002/08/15 03:00:59 momjian Exp $
 -->
 
  <chapter id="libpq">
@@ -942,8 +942,8 @@ strings overlap.
    characters in this binary string (a terminating zero byte is
    neither necessary nor counted).  The <parameter>to_length</parameter>
    parameter shall point to a buffer suitable to hold the resultant
-   escaped string length. The result string length does not
-   include the terminating zero byte of the result.
+   escaped string length. The result string length includes the terminating
+   zero byte of the result.
   </para>
 
   <para>