RE: RI and PARSER (was: Re: [HACKERS] RI status report #1)

What does PENDANT imply/mean in terms of RI? I could figure out all of the
other syntax.

> -----Original Message-----
> From: wieck(at)debis(dot)com [SMTP:wieck(at)debis(dot)com]
> Sent: Wednesday, September 29, 1999 9:03 AM
> To: lockhart(at)alumni(dot)caltech(dot)edu
> 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)
>
> 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) #
>
>
>
> ************