Stephen Robert Norris wrote:

> Well, no. What it says is that certain values must be escaped (but
> doesn't say which ones). Then it says there are alternate escape
> sequences for some values, which it lists.
>
> It doesn't say "The following table contains the characters which must
> be escaped:", which would be much clearer (and actually useful).

Attached documentation patch updates the wording for bytea input
escaping, per complaint by Stephen Norris above.

Joe Conway

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index be63b79c5be935462cde8905ce5f47a114566684..348e1427735fe2dbf80224962762224074703b15 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.119 2003/06/25 03:50:52 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.120 2003/07/18 03:45:06 momjian Exp $
 -->
 
  <chapter id="datatype">
@@ -1062,8 +1062,9 @@ SELECT b, char_length(b) FROM test2;
     literal in an <acronym>SQL</acronym> statement. In general, to
     escape an octet, it is converted into the three-digit octal number
     equivalent of its decimal octet value, and preceded by two
-    backslashes. Some octet values have alternate escape sequences, as
-    shown in <xref linkend="datatype-binary-sqlesc">.
+    backslashes. <xref linkend="datatype-binary-sqlesc"> contains the
+    characters which must be escaped, and gives the alternate escape
+    sequences where applicable.
    </para>
 
    <table id="datatype-binary-sqlesc">