Re: problem with on conflict / do update using psql 14.4 - Mailing list pgsql-general

From Christophe Pettus
Subject Re: problem with on conflict / do update using psql 14.4
Date
Msg-id 65C8502E-7C7F-4F4D-B24B-708284C145F8@thebuild.com
Whole thread Raw
In response to Re: problem with on conflict / do update using psql 14.4  (Barry Kimelman <blkimelman@gmail.com>)
Responses Re: problem with on conflict / do update using psql 14.4
List pgsql-general

> On Sep 24, 2022, at 07:29, Barry Kimelman <blkimelman@gmail.com> wrote:
>
> CREATE UNIQUE INDEX my_companies_company_name_unique ON my_companies(company_name) WHERE delete_timestamp IS NULL;

The issue here is that the unique index is partial (it has a WHERE clause).  In order to use that as an arbiter, you
needinclude a WHERE clause in the ON CONFLICT clause that matches the one on the index. 

I believe that something like:

insert into my_companies (second_id,string_company_id,company_name,person_name)
values (1,'66','widgets','seller-toto')
on conflict (company_name) where delete_timestamp IS NULL do update set company_name =
concat(company_name,'++',string_company_id)

... will work.  Note that if you do an insert with a duplicate "company_name", but "delete_timestamp" not null, it
*won't*treat that as a conflict and won't run the ON CONFLICT action; it'll just insert the row. 


pgsql-general by date:

Previous
From: Barry Kimelman
Date:
Subject: Re: problem with on conflict / do update using psql 14.4
Next
From: Barry Kimelman
Date:
Subject: Re: problem with on conflict / do update using psql 14.4