From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Michael Meskes <Michael_Meskes(at)topmail(dot)de> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Keywords |
Date: | 1999-02-10 15:11:38 |
Message-ID: | 36C1A1AA.92692BE1@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > However, it is handled in a special way: in contexts where one would
> > expect a type name, "int" is translated to "int4" explicitly (very
> > early on, from gram.y). Otherwise it is not translated.
> And int4 is reserved? Is is not in keywords.c though.
No! That's the point, really; there are very few keywords which are type
names. afaik the only cases where type names show up as keywords are
where SQL92 syntax requires special handling, such as "TIMESTAMP WITH
TIME ZONE" and "NATIONAL CHARACTER VARYING". And even in those cases
I've tried to allow as broad a usage as possible, so even though
something is a keyword it may be allowed as a column name, type name, or
identifier unless prohibited by the yacc one-token-lookahead
limitations.
Look in the hardcopy or html User's Guide for the chapter on "Syntax",
which lists the SQL92 and Postgres reserved words. I neglected to add
that chapter to the "integrated docs" (postgres.html) in the last
release, so you will need to look at user.html to find it. Also, it
doesn't include recent changes from Vadim et al for MVCC, which I expect
will add a few keywords eventually.
- Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 1999-02-10 15:23:51 | Re: [HACKERS] Keywords |
Previous Message | Tom Lane | 1999-02-10 15:11:26 | Re: [HACKERS] Re: [GENERAL] A mistake generates strange result |