Re: Supporting multiple column assignment in UPDATE (9.5 project)

Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Fri, May 2, 2014 at 2:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> But I don't think your suggestions of the table name or alias work;
>> they could conflict with an actual column name.

> Presumably it'd follow similar rules to SELECT -- resolve the column
> name in the face of ambiguity.

Meh. Then you could have a query that works fine until you add a column
to the table, and it stops working. If nobody ever used column names
identical to table names it'd be all right, but unfortunately people
seem to do that a lot...

regards, tom lane