Re: INSERT ... ON CONFLICT syntax issues - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: INSERT ... ON CONFLICT syntax issues
Date
Msg-id 553F9F06.80300@2ndquadrant.com
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT syntax issues  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 28/04/15 16:44, Andres Freund wrote:
> On 2015-04-28 10:40:10 -0400, Stephen Frost wrote:
>> * Andres Freund (andres@anarazel.de) wrote:
>>> On 2015-04-28 16:36:28 +0200, Petr Jelinek wrote:
>>>> I am also very sure that every time I'll write this statement I will have to
>>>> look into manual for the names of TARGET and EXCLUDED because they don't
>>>> seem intuitive to me at all (especially the EXCLUDED).
>>>
>>> Same here. I don't understand why 'CONFLICTING' would be more ambiguous
>>> than EXCLUDED (as Peter argued earlier). Especially given that the whole
>>> syntax is called ON CONFLICT.
>>
>> Any way we can alias it?  Both of those strike me as annoyingly long and
>> if we could allow an alias then people can do whatever they want...
>>
>> No, I haven't got any suggestion on how to do that. :)
>>
>> It's also something we can probably improve on in the future...
>
> I earlier suggested NEW/OLD. I still think that's not too bad as I don't
> buy the argument that they're too associated with rules.
>

Hmm, I would never think of rules when talking about NEW/OLD, the 
association I have is with triggers.

--  Petr Jelinek                  http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: INSERT ... ON CONFLICT syntax issues
Next
From: David Steele
Date:
Subject: Re: Proposal: knowing detail of config files via SQL