From fd4c775481f402dda989131edd28d365914cd528 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 18 Jul 2003 03:45:06 +0000
Subject: [PATCH] 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
---
doc/src/sgml/datatype.sgml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index be63b79c5be..348e1427735 100644
--- 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">
--
GitLab