From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Andres Olarte <olarte(dot)andres(at)gmail(dot)com>, Thomas Frieling <frieling(at)8hertz(dot)de>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: CallableStatements: index starts at 2 |
Date: | 2005-12-15 22:19:43 |
Message-ID: | 329C4ADF-A66F-41D0-A9E4-94F198457388@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Well, I was waiting for exactly this report before backpatching
anything.
Dave
On 15-Dec-05, at 5:13 PM, Kris Jurka wrote:
>
>
> On Wed, 14 Dec 2005, Dave Cramer wrote:
>
>> I just checked in a fix for this. It hasn't been well tested on
>> all the various servers so please report problems back to me.
>
> This fix only works on JDK1.4 builds. It doesn't work on 1.2, 1.3,
> or 1.5 because you've only modified Jdbc3CallableStatement. This
> also indicates the fragility of the adjustIndex parameter.
> Unfortunately we can't create an AbstractJdbc2CallableStatement
> because we'd need multiple inheritance for Jdbc3CallableStatement
> to extend both AbstractJdbc3Statement and AbstractJdbc[2|3]
> CallableStatement.
>
> Also your test case using the function getVoid does not work
> against 7.2 servers because the void pseudotype was added in 7.3.
> The void type doesn't seem to be important for testing. You should
> be able to call a function returing anything and ignore the result.
>
> Kris Jurka
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-12-15 22:24:20 | Re: an efficient way of checking if the connection to a db |
Previous Message | Kris Jurka | 2005-12-15 22:14:43 | Re: CallableStatements: index starts at 2 |