Re: JDBC, prepared queries, and partitioning

From: Kris Jurka <books(at)ejurka(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Stephen Denne <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>, PostgreSQL - JDBC <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JDBC, prepared queries, and partitioning
Date: 2008-02-13 22:29:08
Message-ID: Pine.BSO.4.64.0802131724400.2890@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Wed, 13 Feb 2008, Josh Berkus wrote:

> So, just to confirm: there is no way with v3 to make it not use a cached
> plan, either on 8.2 or 8.3, correct?

Correct.

> Can I use v2 against 8.3?
>

Yes, but you then lose some of the features that are only available with
the V3 protocol: ParameterMetaData, some ResultSetMetaData calls, OUT
parameters for CallableStatements. I think that's the list, but couldn't
swear to it.

Kris Jurka

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Simon Riggs 2008-02-13 22:32:45 Re: JDBC, prepared queries, and partitioning
Previous Message Josh Berkus 2008-02-13 22:23:23 Re: JDBC, prepared queries, and partitioning