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

From Tom Lane
Subject Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Date
Msg-id 1502.1486598236@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] BUG #14526: no unique or exclusion constraint matchingthe ON CONFLICT  (David Gould <daveg@sonic.net>)
Responses Re: [BUGS] BUG #14526: no unique or exclusion constraint matchingthe ON CONFLICT  (David Gould <daveg@sonic.net>)
List pgsql-bugs
David Gould <daveg@sonic.net> writes:
> Tom Lane <tgl@sss.pgh.pa.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.

            regards, tom lane


-- 
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: David Gould
Date:
Subject: Re: [BUGS] BUG #14526: no unique or exclusion constraint matchingthe ON CONFLICT
Next
From: David Gould
Date:
Subject: Re: [BUGS] BUG #14526: no unique or exclusion constraint matchingthe ON CONFLICT