Re: Updatable views/with check option parsing
От | Andrew Dunstan |
---|---|
Тема | Re: Updatable views/with check option parsing |
Дата | |
Msg-id | 1762.24.211.165.134.1148678797.squirrel@www.dunslane.net обсуждение исходный текст |
Ответ на | Re: Updatable views/with check option parsing (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: Updatable views/with check option parsing
|
Список | pgsql-hackers |
Peter Eisentraut said: > Martijn van Oosterhout wrote: >> Incidently, IIRC the default behaviour on conflict is a shift anyway, >> so that what the patch already does anyway. >> >> So we get: >> >> CREATE VIEW foo AS SELECT expr :: TIME WITH TIME ZONE <-- OK >> CREATE VIEW foo AS SELECT expr :: TIME WITH CHECK OPTION <-- > >> parse error CREATE VIEW foo AS SELECT (expr :: TIME) WITH CHECK OPTION >> <-- OK > > Yes, that's really the fundamental problem if you let shift/reduce > conflicts stand: the parser will behave weirdly in the conflict cases. > > There is a seemingly little known option in bison named %glr-parser, > which when turned on parses all of theses cases correctly. Maybe that > is worth considering. Interesting. Unfortunately, the manual says: "The GLR parsers require a compiler for ISO C89 or later. In addition, they use the inline keyword, which is not C89, but is C99 and is a common extension in pre-C99 compilers. It is up to the user of these parsers to handle portability issues." Do we want such a restriction? cheers andrew
В списке pgsql-hackers по дате отправления: