Re: [BUGS] BUG #14526: no unique or exclusion constraint matchingthe ON CONFLICT - Mailing list pgsql-bugs

From David Gould
Subject Re: [BUGS] BUG #14526: no unique or exclusion constraint matchingthe ON CONFLICT
Date
Msg-id 20170208153328.1d28f349@engels
Whole thread Raw
In response to Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Wed, 08 Feb 2017 12:31:58 -0500
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Tiago Babo <tiago.babo@gmail.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
continuouslyget the error. I'm using a Scala library called ScalikeJDBC to access the database. So maybe the problem is
onhow it handles the execution. 
 
> 
> You should turn on log_statements and look to see what's actually being
> sent to the server.

Last time I looked, the JDBC driver always uses prepared statements.

-dg

-- 
David Gould              510 282 0869         daveg@sonic.net
If simplicity worked, the world would be overrun with insects.


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: cinbau@warpmail.net
Date:
Subject: [BUGS] BUG #14536: Centos 7 gdal-libs Dependency Problem
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT