Re: differnce from ansi sql standard - unicode strings? - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: differnce from ansi sql standard - unicode strings?
Date
Msg-id 162867790902170733i724e2d22x7a21b0fd0e9100a5@mail.gmail.com
Whole thread Raw
In response to Re: differnce from ansi sql standard - unicode strings?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Hi,

It's possible - I used unofficial BNF graph from internet.

so problem is on my side.

thank you
Pavel


2009/2/17 Peter Eisentraut <peter_e@gmx.net>:
> Pavel Stehule wrote:
>>
>> I found BNF for SQL 2003 and I found there some small difference.
>> Standard use keyword ESCAPE, but PostgreSQL use keybord UESCAPE.
>>
>> Anybody knows reason?
>>
>>  <Unicode character string literal>    ::=
>>         [ <introducer> <character set specification> ]
>>         U <ampersand> <quote> [ <Unicode representation> ... ] <quote>
>>         [ { <separator> <quote> [ <Unicode representation> ... ] <quote>
>> }... ]
>>         [ ESCAPE <escape character> ]
>
> My copy has
>
> <Unicode character string literal> ::=
> [ <introducer><character set specification> ]
> U<ampersand><quote> [ <Unicode representation>... ] <quote>
> [ { <separator> <quote> [ <Unicode representation>... ] <quote> }... ]
> <Unicode escape specifier>
>
> <Unicode escape specifier> ::= [ UESCAPE <quote><Unicode escape
> character><quote> ]
>


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: differnce from ansi sql standard - unicode strings?
Next
From: Tom Lane
Date:
Subject: Re: Questions about parsing boolean and casting to anyelement