From: Ross J. Reedstrom <reedstrm@rice.edu>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-docs@postgresql.org
Subject: Re: SQL keywords
Date: Fri, 15 Dec 2000 17:38:01 -0600
Message-ID: <20001215173801.A32536@rice.edu> (raw)
In-Reply-To: <Pine.LNX.4.30.0012160010410.1319-100000@peter.localdomain>
References: <Pine.LNX.4.30.0012160010410.1319-100000@peter.localdomain>
On Sat, Dec 16, 2000 at 12:29:16AM +0100, Peter Eisentraut wrote:
>
> But does anyone know what they do want to know?
>
> The list of PostgreSQL reserved words seems to be the only thing I can see
> as definitely essential. But which is more important: The list of words
> that are reserved in PG but *not* reserved in SQLxx (i.e., what problems
> can I expect when porting stuff to PG), or the opposite (i.e., what words
> should I avoid when writing portable SQL).
If anyone ever gets around to writing an SQL Flagger (as required for
FIPS 127-2 compliance: the US Federal gov't standard that incorporates
SQL92) they'll need the second list: things in PG not in the standard(s)
Ross
--
Open source code is like a natural resource, it's the result of providing
food and sunshine to programmers, and then staying out of their way.
[...] [It] is not going away because it has utility for both the developers
and users independent of economic motivations. Jim Flynn, Sunnyvale, Calif.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: reedstrm@rice.edu, peter_e@gmx.net
Subject: Re: SQL keywords
In-Reply-To: <20001215173801.A32536@rice.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox