Tom Lane wrote:
> Oliver Jowett <oliver(at)opencloud(dot)com> writes:
>> Another possibility is to make the unnamed statement behaviour in the
>> server more aggressive.
> Upthread I suggested making that conditional on a GUC variable ...
> does that seem reasonable?
That would be fine.
> For instance JDBC would
> need to expose an API to calling applications
I'm not sure why JDBC would need to do this .. in the current driver,
unnamed statements are only used for a single query execution anyway, so
turning on the GUC unconditionally would seem to be the way to go.
In response to
pgsql-jdbc by date
|Next:||From: Simon Riggs||Date: 2008-02-14 07:13:23|
|Subject: Re: JDBC, prepared queries, and partitioning|
|Previous:||From: Tom Lane||Date: 2008-02-14 05:59:26|
|Subject: Re: JDBC, prepared queries, and partitioning |