| From: | David Gould <daveg(at)sonic(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tiago Babo <tiago(dot)babo(at)gmail(dot)com>, 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 23:33:28 |
| Message-ID: | 20170208153328.1d28f349@engels |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 08 Feb 2017 12:31:58 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
Last time I looked, the JDBC driver always uses prepared statements.
-dg
--
David Gould 510 282 0869 daveg(at)sonic(dot)net
If simplicity worked, the world would be overrun with insects.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-02-08 23:57:16 | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |
| Previous Message | cinbau | 2017-02-08 19:56:48 | BUG #14536: Centos 7 gdal-libs Dependency Problem |