From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org (PostgreSQL HACKERS) |
Subject: | scanner/parser for FOREIGN KEY |
Date: | 100-01-03 13:24:05 |
Message-ID: | m1257Sv-0003kGC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 0100-01-03 14:36:53 | pg_dump |
Previous Message | Jan Wieck | 0100-01-03 13:15:09 | Contributors wanted |