Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tiago Babo <tiago(dot)babo(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Date: 2017-02-08 17:31:58
Message-ID: 5285.1486575118@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tiago Babo <tiago(dot)babo(at)gmail(dot)com> writes:
> This is not how my application is doing the insert (like I showed you before), but it was the only way I could continuously get the error. I'm using a Scala library called ScalikeJDBC to access the database. So maybe the problem is on how it handles the execution.

You should turn on log_statements and look to see what's actually being
sent to the server.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2017-02-08 18:38:11 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Previous Message Tiago Babo 2017-02-08 17:26:24 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT