| From: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
|---|---|
| To: | Marti Raudsepp <marti(at)juffo(dot)org> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Support UPDATE table SET(*)=... |
| Date: | 2014-10-15 08:48:25 |
| Message-ID: | CAOeZViff=+O79oOM9CVuwpvJGcfrJc5k=-Aq6ncVUR0zYStQMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday, October 15, 2014, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
> Hi
>
> On Wed, Oct 15, 2014 at 11:02 AM, Atri Sharma <atri(dot)jiit(at)gmail(dot)com
> <javascript:;>> 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).
Regards,
Atri
--
Regards,
Atri
*l'apprenant*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2014-10-15 09:32:52 | Re: Support UPDATE table SET(*)=... |
| Previous Message | Marti Raudsepp | 2014-10-15 08:44:48 | Re: Support UPDATE table SET(*)=... |