Re: differnce from ansi sql standard - unicode strings?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: differnce from ansi sql standard - unicode strings?
Date: 2009-02-17 15:33:51
Message-ID: 162867790902170733i724e2d22x7a21b0fd0e9100a5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)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> ]
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-02-17 15:40:36 Re: Questions about parsing boolean and casting to anyelement
Previous Message Alvaro Herrera 2009-02-17 15:31:35 Re: PL/Perl translation, croak