From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas Lockhart) |
Cc: | wieck(at)debis(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, hackers(at)postgresql(dot)org |
Subject: | Re: RI and PARSER (was: Re: [HACKERS] RI status report #1) |
Date: | 1999-09-29 14:03:05 |
Message-ID: | m11WKK1-0003kLC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Lockhart wrote:
>
> > > > CONSTRAINTS
> > > > DEFERRABLE
> > > > DEFERRED
> > > > IMMEDIATE
> > > > INITIALLY
> > > > PENDANT
> > > > RESTRICT
> > O.K. - I was able to add them all to ColId without conflicts
> > for now. Let's see what happens after adding the syntax for
> > CREATE CONSTRAINT TRIGGER.
>
> Right. Anything which causes trouble can be demoted to ColLabel.
>
> > I'm not sure which of them are SQL92 or SQL3, at least they
> > are all SQL3 "reserved" words according to the SQL3 draft.
>
> According to my Date and Darwen (which is mostly SQL92), all of these
> except "PENDANT" are SQL92 reserved words. PENDANT is not mentioned,
> so is presumably an SQL3-ism.
>
> Do you want me to update syntax.sgml?
Please be so kind. CREATE CONSTRAINT TRIGGER did not mess up
anything, so all these new reserved words appear in ColId and
are still available.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-09-29 14:03:58 | Re: [HACKERS] New notices? |
Previous Message | Tom Lane | 1999-09-29 13:55:15 | Re: [HACKERS] NULL as an argument in plpgsql functions (fwd) |