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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Supporting multiple column assignment in UPDATE (9.5 project)
Date: 2014-05-05 15:32:35
Message-ID: 5367AF13.2060102@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 05/05/2014 11:20 AM, Pavel Stehule wrote:
>
>
>
> How about:
> UPDATE foo SET (foo).* = (1,2,3);
>
>
> It is looking little bit strange
>
> I like previous proposal UPDATE foo SET foo = (1,2,3);
>

What if the table has a field called foo? Won't it then be ambiguous?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2014-05-05 15:33:25 Re: Supporting multiple column assignment in UPDATE (9.5 project)
Previous Message Andrew Dunstan 2014-05-05 15:28:21 Re: 9.4 release notes