| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ON CONFLICT does not support deferrable unique constraints |
| Date: | 2016-08-24 19:22:48 |
| Message-ID: | VisenaEmail.33.379a41fa6f218439.156bdff216d@tc7-visena |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
På onsdag 24. august 2016 kl. 18:36:16, skrev Francisco Olarte <
folarte(at)peoplecall(dot)com <mailto:folarte(at)peoplecall(dot)com>>:
On Wed, Aug 24, 2016 at 6:26 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Wed, Aug 24, 2016 at 6:05 AM, Andreas Joseph Krogh
>> Are there any plans to lift this restriction?
> I'm trying to figure out a method for making this work in my head.
> These two things seem kind of opposed to each other.
He probably wants to just treat is as non-deferrable just during the
upsert. I do not know if he has thought this opens a can of worms (
like, the constraint may be already broken due to precious DML ).
Francisco Olarte.
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.
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Farber | 2016-08-24 20:27:27 | Re: Forward declaration of table |
| Previous Message | Francisco Olarte | 2016-08-24 16:36:16 | Re: ON CONFLICT does not support deferrable unique constraints |