Re: EXECUTE command tag returns actual command - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: EXECUTE command tag returns actual command
Date
Msg-id 3739.1082434505@sss.pgh.pa.us
Whole thread Raw
In response to Re: EXECUTE command tag returns actual command  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [PATCHES] EXECUTE command tag returns actual command  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-jdbc
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Your patch has been added to the PostgreSQL unapplied patches list at:

> Kris Jurka wrote:
>> This patch makes the EXECUTE command's completion tag return the
>> completion tag of the actual statement executed.

While I don't have any strong reason to object to this, the reason
Kris wanted it was to help let the JDBC driver use "EXECUTE prepared-stmt"
as its basic mechanism for executing pre-prepared statements --- and
there are a couple reasons why he should abandon that idea in favor of
using V3-protocol Bind/Execute messages.

If he goes over to using Bind/Execute then the JDBC driver will have no
need for this patch.  In that case we ought to stop and think whether
sticking to the existing behavior isn't the right thing to do; it wins
on backwards-compatibility grounds and we have no other use-cases saying
we should change.

Not a big complaint, but something to consider before applying.

            regards, tom lane

PS: If you do apply, the EXECUTE reference page needs to have an
"Output" section added explaining that it returns a tag other than the
default "EXECUTE".

pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Prepared Statements and large where-id-in constant blocks?
Next
From: Anton Komarevtsev
Date:
Subject: Re: binary data in `bytea' column