scanner/parser for FOREIGN KEY - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject scanner/parser for FOREIGN KEY
Date
Msg-id m1257Sv-0003kGC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
Responses Re: [HACKERS] scanner/parser for FOREIGN KEY
List pgsql-hackers
Hi,

    we  still need the enhancement of the scanner/parser combo to
    enable FOREIGN KEY specification as  column  constraint  (the
    due to shift/reduce disabled NOT DEFERRABLE part).

    IMHO this must be done before going into BETA.  As discussed,
    a little token lookup/queueing between lex and  yacc  can  do
    the  trick. I'd like to add a slightly generic method for it,
    so the lookahead function can be reused if we  sometimes  get
    trapped again with a similar problem.

    Do we have a consensus to implement it that way now?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Contributors wanted
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: pg_dump