Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 4b836d8

Browse filesBrowse files
committed
Add some links for escape strings.
Brendan Jurd Fix markup in previous commit.
1 parent f6a168e commit 4b836d8
Copy full SHA for 4b836d8

File tree

Expand file treeCollapse file tree

2 files changed

+13
-12
lines changed
Filter options
Expand file treeCollapse file tree

2 files changed

+13
-12
lines changed

‎doc/src/sgml/func.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/func.sgml
+10-10Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.393 2007/09/14 00:52:45 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.394 2007/09/14 14:54:25 momjian Exp $ -->
22

33
<chapter id="functions">
44
<title>Functions and Operators</title>
@@ -2929,14 +2929,14 @@ cast(-44 as bit(12)) <lineannotation>111111010100</lineannotation>
29292929
</para>
29302930

29312931
<para>
2932-
Note that the backslash already has a special meaning in string
2933-
literals, so to write a pattern constant that contains a backslash
2934-
you must write two backslashes in an SQL statement (assuming escape
2935-
string syntax is used). Thus, writing a pattern
2936-
that actually matches a literal backslash means writing four backslashes
2937-
in the statement. You can avoid this by selecting a different escape
2938-
character with <literal>ESCAPE</literal>; then a backslash is not special
2939-
to <function>LIKE</function> anymore. (But it is still special to the string
2932+
Note that the backslash already has a special meaning in string literals,
2933+
so to write a pattern constant that contains a backslash you must write two
2934+
backslashes in an SQL statement (assuming escape string syntax is used, see
2935+
<xref linkend="sql-syntax-strings">). Thus, writing a pattern that
2936+
actually matches a literal backslash means writing four backslashes in the
2937+
statement. You can avoid this by selecting a different escape character
2938+
with <literal>ESCAPE</literal>; then a backslash is not special to
2939+
<function>LIKE</function> anymore. (But it is still special to the string
29402940
literal parser, so you still need two of them.)
29412941
</para>
29422942

@@ -3549,7 +3549,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
35493549
meaning in <productname>PostgreSQL</> string literals.
35503550
To write a pattern constant that contains a backslash,
35513551
you must write two backslashes in the statement, assuming escape
3552-
string syntax is used.
3552+
string syntax is used (see <xref linkend="sql-syntax-strings">).
35533553
</para>
35543554
</note>
35553555

‎doc/src/sgml/libpq.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/libpq.sgml
+3-2Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.244 2007/09/14 14:31:22 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.245 2007/09/14 14:54:25 momjian Exp $ -->
22

33
<chapter id="libpq">
44
<title><application>libpq</application> - C Library</title>
@@ -5097,7 +5097,8 @@ defaultNoticeProcessor(void *arg, const char *message)
50975097
user=appuser
50985098
ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
50995099
</synopsis>
5100-
<para>
5100+
</para>
5101+
51015102
</sect1>
51025103

51035104

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.