Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28])
	by mail.postgresql.org (8.11.1/8.11.1) with SMTP id eBI3uG641505
	for <pgsql-docs@postgresql.org>; Sun, 17 Dec 2000 22:56:16 -0500 (EST)
	(envelope-from pgsql-docs-owner@postgresql.org)
Received: from news.tht.net (news.hub.org [216.126.91.242])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBG970620251
	for <pgsql-docs@postgresql.org>; Sat, 16 Dec 2000 04:07:00 -0500 (EST)
	(envelope-from news@news.tht.net)
Received: (from news@localhost) by news.tht.net (8.9.3/8.9.3) id DAA80588
	for pgsql-docs@postgresql.org; Sat, 16 Dec 2000 03:47:59 -0500 (EST)
	(envelope-from news)
X-Authentication-Warning: news.tht.net: news set sender to <news> using -f
From: Emmanuel Charpentier <charpent@bacbuc.dyndns.org>
X-Newsgroups: comp.databases.postgresql.docs
Subject: Re: SQL keywords
Date: Sat, 16 Dec 2000 08:47:58 GMT
Organization: Hub.Org Networking Services (http://www.hub.org)
Lines: 50
Message-ID: <20001216.8475800@aleph.bacbuc.dyndns.org>
References: <3A3B2310.EB5C3DEE@tm.ee>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: news.tht.net 976956479 80585 193.251.31.31 (16 Dec 2000 08:47:59 GMT)
X-Complaints-To: scrappy@hub.org
X-Priority: 3 (Normal)
X-Newsreader: Mozilla/3.0 (compatible; StarOffice/5.2;Linux)
To: pgsql-docs@postgresql.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.postgresql.org id
	eBG971620252
X-Archive-Number: 200012/45
X-Sequence-Number: 92

Hi !

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

Le 12/16/00, à 9:14:16 AM h, hannu@tm.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