| 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-09 02:00:40 |
| Message-ID: | 20170208180040.0e2b4891@engels |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 08 Feb 2017 18:57:16 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> David Gould <daveg(at)sonic(dot)net> writes:
> > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> 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.
>
> Yeah, but does JDBC actually pull literal constants out of the query
> string and send them as separate parameter values? That seems like a
> pretty dumb idea.
I'm guessing that the actual call from Scala uses parameters for this
part instead of duplicating the same query with only the qualification
changing.
Tiago, can you show us the actual code that runs this statement?
-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 | 片本 亘祐（ユニークビジョン） | 2017-02-09 02:28:50 | |
| Previous Message | Tom Lane | 2017-02-08 23:57:16 | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |