Re: [HACKERS] why is char now a keyword - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] why is char now a keyword
Date
Msg-id f92662ecc6f97c81b15e484d33502e7e
Whole thread Raw
List pgsql-hackers
Edmund Mergl wrote:

> Hi all,
>
> the current snapshot reserves 'char' as keyword.
> Can anyone tell me the reason ?

At least in part so that we can do the explicit parsing required to
support SQL92 syntax elements such as "character sets" and "collating
sequences". I'd like to get support for multiple character sets, but am
immersed in documentation so will not likely get to this for the next
release. Have you encountered a problem with an existing database? In
what context??

                                                      - Tom

------------------------------

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Next
From: Bruce Momjian
Date:
Subject: Re: consttraints.source