Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 39ceedf

Browse files
committed
The regexp pattern characters ^ and $ should be explained as matching
at the beginning and end of the input string, not the beginning and end of "a line", since Postgres does not allow them to match at newline characters in the data.
1 parent 42eaad0 commit 39ceedf

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/src/sgml/func.sgml

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.55 2001/03/15 01:07:51 tgl Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.56 2001/03/25 18:14:31 tgl Exp $ -->
22

33
<chapter id="functions">
44
<title>Functions and Operators</title>
@@ -1205,9 +1205,9 @@
12051205
expression), an empty set of <literal>()</literal> (matching the
12061206
null string), a <firstterm>bracket expression</firstterm> (see
12071207
below), <literal>.</literal> (matching any single character),
1208-
<literal>^</literal> (matching the null string at the beginning of
1209-
a line), <literal>$</literal> (matching the null string at the end
1210-
of a line), a <literal>\</literal> followed by one of the
1208+
<literal>^</literal> (matching the null string at the beginning of the
1209+
input string), <literal>$</literal> (matching the null string at the end
1210+
of the input string), a <literal>\</literal> followed by one of the
12111211
characters <literal>^.[$()|*+?{\</literal> (matching that
12121212
character taken as an ordinary character), a <literal>\</literal>
12131213
followed by any other character (matching that character taken as

0 commit comments

Comments
 (0)