On Sat, Sep 24, 2022 at 10:56 AM Christophe Pettus wrote:
>
>
> > On Sep 24, 2022, at 08:49, Barry Kimelman wrote:
> > I thought the whole point of ON CONFLICT DO UPDATE was so that you could
> modify the data so that it would be inserted
>
> ON CONFLICT DO UPDA
On Sat, Sep 24, 2022 at 10:44 AM Christophe Pettus wrote:
>
>
> > On Sep 24, 2022, at 08:29, Barry Kimelman wrote:
> > Thanks for the response. When I ran the INSERT with your suggested
> change I got an error message telling me
> > "column reference &#x
On Sat, Sep 24, 2022 at 9:47 AM Christophe Pettus wrote:
>
>
> > On Sep 24, 2022, at 07:29, Barry Kimelman wrote:
> >
> > CREATE UNIQUE INDEX my_companies_company_name_unique ON
> my_companies(company_name) WHERE delete_timestamp IS NULL;
>
> The issue here is
On Fri, Sep 23, 2022 at 4:42 PM Steve Baldwin
wrote:
> You need to prefix the rhs column(s) with 'excluded.'. For example:
>
> on conflict (company_name) do update set company_name =
> concat(excluded.company_name,'++',excluded.string_company_id);
>
>
On Fri, Sep 23, 2022 at 4:43 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Fri, Sep 23, 2022 at 2:28 PM Barry Kimelman
> wrote:
>
>>
>> CREATE UNIQUE INDEX my_companies_id_unique ON
>> my_companies(string_company_id) WHERE delete_timestam
I have not been able to get the "ON CONFLICT" clause to work
I am using psql 14.4 on ubuntu
Given the following table definition
CREATE TABLE my_companies (
company_id SERIAL NOT NULL PRIMARY KEY,
second_id INTEGER NOT NULL REFERENCES big_list(second_id),
string_company_id TEXT NOT NULL,
