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

> > CONSTRAINTS
> > DEFERRABLE
> > DEFERRED
> > IMMEDIATE
> > INITIALLY
> > PENDANT
> > RESTRICT
>
> [...]
> allowed column and table names. The keywords, reserved, unreserved,
> and unused, are documented for Postgres in syntax.sgml, and the docs
> present them wrt the SQL92 and SQL3 standards.
>
> What I usually do is try adding one or all of them to ColId, and if
> that fails by giving shift/reduce conflicts I'll try moving the
> offenders to ColLabel. There aren't many places in the syntax where
> yacc/bison can't handle keywords at least as column labels.

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.

I'm not sure which of them are SQL92 or SQL3, at least they
are all SQL3 "reserved" words according to the SQL3 draft.

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) #