From 7b6fb76349fccc38f0ef96166f207c6acd21968c Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Tue, 10 Nov 2015 22:11:39 -0500 Subject: [PATCH] Docs: fix misleading example. Commit 8457d0beca731bf0 introduced an example which, while not incorrect, failed to exhibit the behavior it meant to describe, as a result of omitting an E'' prefix that needed to be there. Noticed and fixed by Peter Geoghegan. I (tgl) failed to resist the temptation to wordsmith nearby text a bit while at it. --- doc/src/sgml/datatype.sgml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 4d883ecb8b..b5191f4536 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1100,14 +1100,15 @@ SELECT '52093.89'::money::numeric::float8; stored and displayed that way. However, trailing spaces are treated as semantically insignificant and disregarded when comparing two values of type character. In collations where whitespace - is significant, this behavior can produce unexpected results, - e.g. SELECT 'a '::CHAR(2) collate "C" < - 'a\n'::CHAR(2) returns true. + is significant, this behavior can produce unexpected results; + for example SELECT 'a '::CHAR(2) collate "C" < + E'a\n'::CHAR(2) returns true, even though C + locale would consider a space to be greater than a newline. Trailing spaces are removed when converting a character value to one of the other string types. Note that trailing spaces are semantically significant in character varying and text values, and - when using pattern matching, e.g. LIKE, + when using pattern matching, that is LIKE and regular expressions. -- 2.40.0