Re: [PATCHES] Linkage for escape strings

2007-09-14 Thread Bruce Momjian

Patch applied.  Thanks.  Your documentation changes can be viewed in
five minutes using links on the developer's page,
http://www.postgresql.org/developer/testing.

---


Brendan Jurd wrote:
 Just a minor doc upgrade.  I've linked a couple of the more prominent
 mentions of escape string syntax in Functions and Operators /
 Pattern Matching back to the section on SQL string literals, which
 explains how escape syntax works.
 
 I considering linking all mentions of escape syntax, but thought that
 might be overkill since there are so many of them.
 
 Thanks for your time,
 BJ

[ Attachment, skipping... ]

 
 ---(end of broadcast)---
 TIP 3: Have you checked our extensive FAQ?
 
http://www.postgresql.org/docs/faq

-- 
  Bruce Momjian  [EMAIL PROTECTED]  http://momjian.us
  EnterpriseDB   http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org


[PATCHES] Linkage for escape strings

2007-09-01 Thread Brendan Jurd
Just a minor doc upgrade.  I've linked a couple of the more prominent
mentions of escape string syntax in Functions and Operators /
Pattern Matching back to the section on SQL string literals, which
explains how escape syntax works.

I considering linking all mentions of escape syntax, but thought that
might be overkill since there are so many of them.

Thanks for your time,
BJ
Index: doc/src/sgml/func.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/func.sgml,v
retrieving revision 1.392
diff -c -r1.392 func.sgml
*** doc/src/sgml/func.sgml  31 Aug 2007 21:33:48 -  1.392
--- doc/src/sgml/func.sgml  1 Sep 2007 17:09:45 -
***
*** 2929,2942 
 /para
  
 para
! Note that the backslash already has a special meaning in string
! literals, so to write a pattern constant that contains a backslash
! you must write two backslashes in an SQL statement (assuming escape
! string syntax is used).  Thus, writing a pattern
! that actually matches a literal backslash means writing four backslashes
! in the statement.  You can avoid this by selecting a different escape
! character with literalESCAPE/literal; then a backslash is not special
! to functionLIKE/function anymore. (But it is still special to the 
string
  literal parser, so you still need two of them.)
 /para
  
--- 2929,2942 
 /para
  
 para
! Note that the backslash already has a special meaning in string literals,
! so to write a pattern constant that contains a backslash you must write 
two
! backslashes in an SQL statement (assuming escape string syntax is used, 
see
! xref linkend=sql-syntax-strings).  Thus, writing a pattern that
! actually matches a literal backslash means writing four backslashes in the
! statement.  You can avoid this by selecting a different escape character
! with literalESCAPE/literal; then a backslash is not special to
! functionLIKE/function anymore. (But it is still special to the string
  literal parser, so you still need two of them.)
 /para
  
***
*** 3549,3555 
   meaning in productnamePostgreSQL/ string literals.
   To write a pattern constant that contains a backslash,
   you must write two backslashes in the statement, assuming escape
!  string syntax is used.
  /para
 /note
  
--- 3549,3555 
   meaning in productnamePostgreSQL/ string literals.
   To write a pattern constant that contains a backslash,
   you must write two backslashes in the statement, assuming escape
!  string syntax is used (see xref linkend=sql-syntax-strings).
  /para
 /note
  

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq