Re: ON CONFLICT does not support deferrable unique constraints
От | Francisco Olarte |
---|---|
Тема | Re: ON CONFLICT does not support deferrable unique constraints |
Дата | |
Msg-id | CA+bJJbz_XRAgfc=6bsuzMtO6iynOoqDDCL1UHiW1mzrcWUkd-Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ON CONFLICT does not support deferrable unique constraints (Andreas Joseph Krogh <andreas@visena.com>) |
Ответы |
Re: ON CONFLICT does not support deferrable unique constraints
|
Список | pgsql-general |
On Wed, Aug 24, 2016 at 9:22 PM, Andreas Joseph Krogh <andreas@visena.com> wrote: > As a developer I want it to "just work", if there's an error of any kind then abort the transaction, just as it was non-deferrable. Everybody wants everything to "just work", for their own ( in a lot of cases unspecified even to the themselves ) definition of JW. Developers normally want to be told what "just work" means when developing something. That been said, I'm not sure making it ( deferred constraint act like immediate ones during upserts ) work is even a good idea. If it can be conditionally enabled with a simple set and implemented in very few ( < 20 ) lines of code, ok for me , otherwise I would prefer the reduced bug surface. Francisco Olarte.
В списке pgsql-general по дате отправления: