Re: ON CONFLlCT DO UPDATE command cannot affect row a second time

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: ON CONFLlCT DO UPDATE command cannot affect row a second time
Дата
Msg-id CAKFQuwbG07-m3t2HJ1S36T4wK2mQdYOuuU8R+OK65u8Y5fLuvw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: ON CONFLlCT DO UPDATE command cannot affect row a second time  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-novice
On Thursday, April 30, 2020, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Thursday, April 30, 2020, cryptodactyl <adriann.muresan@gmail.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.


Oh removing python from the problem space is a solid next step, the server is raising the error so it should be doable to use a psql script to duplicate the problem.

David J.
 

В списке pgsql-novice по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: ON CONFLlCT DO UPDATE command cannot affect row a second time
Следующее
От: JORGE MALDONADO
Дата:
Сообщение: Unique Constraint vs Unique Index