Excerpts from Alvaro Herrera's message of mié ago 03 13:12:38 -0400 2011:
> ... ah, maybe what we could do is have gram.y create a ColumnDef in the
> new production, and stick that in cmd->def instead of the list of
> constraints. So parse_utilcmd would have to know that if that node
> IsA(ColumnDef) then it needs to deal with column constraints. It seems
> a bit cleaner overall, though it's still wart-ish.
Yes, this works, thanks for the suggestion. Attached.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
