"Pavlo Baron" <pb@pbit.org> writes:
> 3. gram.y - here I added a rule for the DEFAULT-element in the target_list
> used for the INSERT-statement. It now replaces DEFAULT by an anti-thing like
> "@default" because I couldn't find out were it fails if I leave DEFAULT
> unchainged. If smb. knows a way to do it I'll drop this @default
This would breakINSERT INTO foo(textcolumn) VALUES ('@default')
which I find hardly acceptable.
The only way to do it without breaking valid data entries is to
introduce a new parse node type to represent a DEFAULT placeholder.
I also wonder what's going to happen if I write DEFAULT in a SELECT's
targetlist, which is possible given where you made the grammar change.
regards, tom lane