| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Edmund Mergl <E(dot)Mergl(at)bawue(dot)de> |
| Cc: | PostgreSQL Developers Mailinglist <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] why is char now a keyword |
| Date: | 1998-01-05 07:56:07 |
| Message-ID: | 34B09217.1E292BDC@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vadim B. Mikheev | 1998-01-05 12:35:59 | Re: [HACKERS] subselect |
| Previous Message | Vadim B. Mikheev | 1998-01-05 07:48:59 | Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c') |