| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | cryptodactyl <adriann(dot)muresan(at)gmail(dot)com> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: ON CONFLlCT DO UPDATE command cannot affect row a second time |
| Date: | 2020-04-30 18:07:55 |
| Message-ID: | CAKFQuwYMXw5B5SAw2LGuQzJ9rSxrOZ0W+G1jQYse_2SEWKXSLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Thursday, April 30, 2020, cryptodactyl <adriann(dot)muresan(at)gmail(dot)com> wrote:
>
> HINT: Ensure that no rows proposed for insertion within the same command
> have duplicate constrained values.
>
Its related to specific data yet you haven’t provided any...even if you
cannot share the original data without a self-contained test case
demonstrating the problem the odds of getting answers is quite low (not
that i’m an on conflict expert).
I'm not a database guy and certainly not a Python expert. How do I fix this
Learn enough so you can provide good info to others who can maybe help you
or turn the over the problem to someone who has more experience in this
area.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-04-30 18:09:38 | Re: ON CONFLlCT DO UPDATE command cannot affect row a second time |
| Previous Message | cryptodactyl | 2020-04-30 17:27:04 | ON CONFLlCT DO UPDATE command cannot affect row a second time |