pgsql: Refactor ecpg grammar so that it uses the core grammar's
От | tgl@postgresql.org (Tom Lane) |
---|---|
Тема | pgsql: Refactor ecpg grammar so that it uses the core grammar's |
Дата | |
Msg-id | 20091121054406.14181753FB7@cvs.postgresql.org обсуждение исходный текст |
Список | pgsql-committers |
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. Modified Files: -------------- pgsql/src/interfaces/ecpg/preproc: ecpg.trailer (r1.14 -> r1.15) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/ecpg.trailer?r1=1.14&r2=1.15) ecpg.type (r1.2 -> r1.3) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/ecpg.type?r1=1.2&r2=1.3) parse.pl (r1.4 -> r1.5) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/parse.pl?r1=1.4&r2=1.5)
В списке pgsql-committers по дате отправления: