database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-09 18:21:05 +03:00
Code

Add some links for escape strings.

Browse Source 
Brendan Jurd

Fix markup in previous commit.
This commit is contained in:
Bruce Momjian 2007-09-14 14:54:25 +00:00
parent f6a168e2c3
commit 4b836d8312
2 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/src/sgml/func.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.393 2007/09/14 00:52:45 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.394 2007/09/14 14:54:25 momjian Exp $ -->
<chapter id="functions"> <chapter id="functions">
<title>Functions and Operators</title> <title>Functions and Operators</title>
@ -2929,14 +2929,14 @@ cast(-44 as bit(12)) <lineannotation>111111010100</lineannotation>
</para> </para>
<para> <para>
Note that the backslash already has a special meaning in string Note that the backslash already has a special meaning in string literals,
literals, so to write a pattern constant that contains a backslash so to write a pattern constant that contains a backslash you must write two
you must write two backslashes in an SQL statement (assuming escape backslashes in an SQL statement (assuming escape string syntax is used, see
string syntax is used). Thus, writing a pattern <xref linkend="sql-syntax-strings">). Thus, writing a pattern that
that actually matches a literal backslash means writing four backslashes actually matches a literal backslash means writing four backslashes in the
in the statement. You can avoid this by selecting a different escape statement. You can avoid this by selecting a different escape character
character with <literal>ESCAPE</literal>; then a backslash is not special with <literal>ESCAPE</literal>; then a backslash is not special to
to <function>LIKE</function> anymore. (But it is still special to the string <function>LIKE</function> anymore. (But it is still special to the string
literal parser, so you still need two of them.) literal parser, so you still need two of them.)
</para> </para>
@ -3549,7 +3549,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
meaning in <productname>PostgreSQL</> string literals. meaning in <productname>PostgreSQL</> string literals.
To write a pattern constant that contains a backslash, To write a pattern constant that contains a backslash,
you must write two backslashes in the statement, assuming escape you must write two backslashes in the statement, assuming escape
string syntax is used. string syntax is used (see <xref linkend="sql-syntax-strings">).
</para> </para>
</note> </note>

5
doc/src/sgml/libpq.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.244 2007/09/14 14:31:22 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.245 2007/09/14 14:54:25 momjian Exp $ -->
<chapter id="libpq"> <chapter id="libpq">
<title><application>libpq</application> - C Library</title> <title><application>libpq</application> - C Library</title>
@ -5097,7 +5097,8 @@ defaultNoticeProcessor(void *arg, const char *message)
user=appuser user=appuser
ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*) ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
</synopsis> </synopsis>
<para> </para>
</sect1> </sect1>