Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint

On 20 May 2015 at 05:49, Geoff Winkless <pgsqladmin(at)geoff(dot)dj> wrote:

> On 19 May 2015 at 21:57, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
>> It's not clear to me how a single INSERT could cause two or more UPDATEs.
>>
>
> ​
> CREATE TABLE mytable (
> c1 int NOT NULL,
> c2 int NOT NULL,
> PRIMARY KEY (c1),
> UNIQUE (c2)​
>
> ​);
>
> INSERT INTO mytable (c1, c2) (10, 20);​
> INSERT INTO mytable (c1, c2) (11, 21);
> ​INSERT INTO mytable (c1, c2) (10, 21) ON CONFLICT DO UPDATE .....
> ​
> Or did you mean from a coding point of view how it would be possible to
> implement?
>

I mean "how could that possibly have useful meaning?".

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services