From: | Greg Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unicode string literals versus the world |
Date: | 2009-04-15 17:57:22 |
Message-ID: | 4136ffa0904151057h27b6e3a2jc1c124d5f5b43098@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 15, 2009 at 6:52 PM, Greg Stark <stark(at)enterprisedb(dot)com> wrote:
> On Wed, Apr 15, 2009 at 6:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Wouldn't we just then say that U&'' strings are always standard-
>>> conforming?
>>
>> That's exactly what's causing the problem --- they are, but there
>> is lots of software that won't know it.
>
>
> We could say U&'' escapes only work if you have
> standards_conforming_strings set to true.
Or say that if you have standards_conforming_strings false then any
string which contains a literal \ or ' is an error. You shouldn't ever
really need either since you could use the unicode escape for either
after all.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2009-04-15 18:06:04 | Re: Unicode string literals versus the world |
Previous Message | Simon Riggs | 2009-04-15 17:56:03 | Re: New trigger option of pg_standby |