Re: SET syntax in INSERT - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: SET syntax in INSERT
Date
Msg-id CAKFQuwaq--9CAwAgRvZCjwPPx4MX6CW54sSnsroNHQywFi-jqQ@mail.gmail.com
Whole thread Raw
In response to Re: SET syntax in INSERT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SET syntax in INSERT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On Thu, Jan 14, 2016 at 1:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Vitaly Burovoy <vitaly.burovoy@gmail.com> writes:
> On 1/14/16, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It's more than syntactic sugar; you are going to have to invent semantics,
>> as well, because it's less than clear what partial-field assignments
>> should do.
>>
>> Assume a table with an int-array column, and consider
>> INSERT INTO foo SET arraycol[2] = 7, arraycol[4] = 11;

> Right part is a column name, not an expression. Isn't it?
 

> You can't now do something like
> INSERT INTO foo (arraycol[2], arraycol[4]) VALUES(7, 11);

Hm ... actually, you might want to try that before opining

​So what's the problem, then?  It seems like a decision has already been made.

David J.

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: SET syntax in INSERT
Next
From: Vitaly Burovoy
Date:
Subject: Re: SET syntax in INSERT