Postgres Pro
Downloads
Home   >   mailing lists

Re: Support UPDATE table SET(*)=... - Mailing list pgsql-hackers

From Atri Sharma
Subject Re: Support UPDATE table SET(*)=...
Date
Msg-id CAOeZViePTEb8f7GV96DBNDsEGQV9VpDPexfh6w8yntvtQzvQYA@mail.gmail.com
Whole thread Raw
In response to Re: Support UPDATE table SET(*)=...  (Atri Sharma <atri.jiit@gmail.com>)
List pgsql-hackers
Tree view


On Wed, Oct 15, 2014 at 2:18 PM, Atri Sharma <atri.jiit@gmail.com> wrote:





On Wednesday, October 15, 2014, Marti Raudsepp <marti@juffo.org> wrote:
Hi

On Wed, Oct 15, 2014 at 11:02 AM, Atri Sharma <atri.jiit@gmail.com> wrote:
> Please find attached a patch which implements support for UPDATE table1
> SET(*)=...

I presume you haven't read Tom Lane's proposal and discussion about
multiple column assignment in UPDATE:
http://www.postgresql.org/message-id/1783.1399054541@sss.pgh.pa.us
(Assigning all columns was also discussed there)

And there's a WIP patch:
http://www.postgresql.org/message-id/20930.1402931841@sss.pgh.pa.us



Thanks for the links, but this patch only targets SET(*) case, which, if I understand correctly, the patch you mentioned doesn't directly handle (If I understand correctly, the target of the two patches is different). 


Digging more, I figured that the patch I posted builds on top of Tom's patch,  since it did not add whole row cases.

Regards,

Atri

pgsql-hackers by date:

Previous
From: Atri Sharma
Date:
Subject: Re: Support UPDATE table SET(*)=...
Next
From: Ali Akbar
Date:
Subject: Re: proposal: plpgsql - Assert statement