pgsql: Refactor ecpg grammar so that it uses the core grammar's

Started by Tom Laneover 16 years ago1 messagescomitters

tgl@sss.pgh.pa.us

over 16 years ago

Log Message:
-----------
Refactor ecpg grammar so that it uses the core grammar's unreserved_keyword
list, minus a few specific words that have to be treated specially. This
replaces a hard-wired list of keywords that would have needed manual
maintenance, and was not getting it. The 8.4 coding was already missing
these words, causing ecpg to incorrectly treat them as reserved words:
CALLED, CATALOG, DEFINER, ENUM, FOLLOWING, INVOKER, OPTIONS, PARTITION,
PRECEDING, RANGE, SECURITY, SERVER, UNBOUNDED, WRAPPER. In HEAD we were
additionally missing COMMENTS, FUNCTIONS, SEQUENCES, TABLES.
Per gripe from Bosco Rama.

Tags:
----
REL8_4_STABLE

Modified Files:
--------------
pgsql/src/interfaces/ecpg/preproc:
ecpg.trailer (r1.9 -> r1.9.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/ecpg.trailer?r1=1.9&r2=1.9.2.1)
ecpg.type (r1.1 -> r1.1.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/ecpg.type?r1=1.1&r2=1.1.2.1)
parse.pl (r1.3 -> r1.3.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/parse.pl?r1=1.3&r2=1.3.2.1)