Re: SQL keywords

From: Emmanuel Charpentier <charpent(at)bacbuc(dot)dyndns(dot)org>
To: pgsql-docs(at)postgresql(dot)org
Subject: Re: SQL keywords
Date: 2000-12-16 08:47:58
Message-ID: 20001216.8475800@aleph.bacbuc.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hi !

>>>>>>>>>>>>>>>>>> Message d'origine <<<<<<<<<<<<<<<<<<

Le 12/16/00, à 9:14:16 AM h, hannu(at)tm(dot)ee (Hannu Krosing) vous a écrit sur
le sujet suivant Re: [DOCS] SQL keywords:

> Peter Eisentraut wrote:
> >
> > The section on SQL keywords in the User's Guide needs some updating.
> >
> > I figured that I could generate these various lists of reserved and
> > non-reserved keywords automatically --- and indeed I can!

[ bandwidth savings ... ]

> It could be a good thing to have a table of the form

> Keyword | PostgreSQL | SQL 92 | SQL 99 |
> -----------+--------------+-------------+-------------+
> SELECT | Reserved | Reserved | Reserved |
> WITH | - | - | Reserved |
> IN | Yes | - | Reserved |

Hmmm ...

Better make that
Keyword | Standard | Status |
------------+-----------+---------+
SELECT | SQL92 | Reserved|
SELECT | SQL99 | Reserved|
SELECT | PostgreSQL| Reserved|
WITH | SQL92 | Nope |
WITH | SQL99 | Reserved|
WITH | PostgeSQL | Nope |
IN | SQL92 | Nope |
IN | SQL99 | Reserved|
IN | PostgreSQL| Yep |

This form allows for greater flexibility in query/views building. Obvious
drawback : the primary key is composite.

Any thoughts ?

Emmanuel Charpentier

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Peter Eisentraut 2000-12-16 18:29:53 Re: SQL keywords
Previous Message Hannu Krosing 2000-12-16 08:08:48 Re: SQL keywords