Message-ID: <48188201.6010304@postnewspapers.com.au>
Date: Wed, 30 Apr 2008 22:28:17 +0800
From: Craig Ringer <craig@postnewspapers.com.au>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Andy Anderson <aanderson@amherst.edu>
Cc: pgsql-general@postgresql.org
Subject: Re: Quoting "
References: <D08F79F6-8401-4503-BB09-56EAEF47714F@amherst.edu>
In-Reply-To: <D08F79F6-8401-4503-BB09-56EAEF47714F@amherst.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Andy Anderson wrote:
> In a test I just did, the sequence \" (backslash double-quote) is 
> interpreted as just a " inside of the E'...' string constant expression. 
> This is great, since PHP's addslashes() sticks them in along with the 
> other stuff I really need to quote like ' and \. But I see that \" isn't 
> documented in the manual in section 4.1.2.1. I assume this is, in fact, 
> standard behavior for Postgres? (Perhaps a comprehensive table might be 
> a good idea at this point in the manual.)

craig=# SELECT E'\z\v\k\-';
  ?column?
----------
  zvk-
(1 row)

 From 4.1.2.1:

... "Any other character following a backslash is taken literally."

I didn't see any escape sequences being interpreted other than those 
that're already documented in the section of 4.1.2.1 that describes E'' 
strings.

--
Craig Ringer