Re: JDBC, prepared queries, and partitioning - Mailing list pgsql-jdbc

From Simon Riggs
Subject Re: JDBC, prepared queries, and partitioning
Date
Msg-id 1202975013.16770.594.camel@ebony.site
Whole thread Raw
In response to Re: JDBC, prepared queries, and partitioning  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: JDBC, prepared queries, and partitioning  (Oliver Jowett <oliver@opencloud.com>)
List pgsql-jdbc
On Thu, 2008-02-14 at 20:18 +1300, Oliver Jowett wrote:
> Simon Riggs wrote:
>
> > But V3 supports having no parameters at all right?
>
> Yes, but you're missing the point. If you want to, for example, ask for
> metadata about the 4th parameter to the query, there has to *be* a 4th
> parameter. If you fold everything inline, you lose the various
> advantages that having the parameters out of line give you, such as the
> ability to query the server about their characteristics or stream their
> actual values in a binary form separate to the query, etc.

Right now, people are choosing to use V2 because of the
parameter-folding characteristics. Those people are giving up the things
you mention, plus much much more. I'm suggesting that we make the
parameter folding an option, to allow people to choose. If they need
access to parameter metadata (or other possibilities) then they won't
take advantage of the parameter-folding option.

I suggest we put the parameter folding option in now, then in 8.4 keep
the option but make it work via a GUC as Tom suggests.

--
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com


pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: JDBC, prepared queries, and partitioning
Next
From: Oliver Jowett
Date:
Subject: Re: JDBC, prepared queries, and partitioning