From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(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:13:04 |
Message-ID: | Pine.BSO.4.61.0512151706510.17948@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2005-12-15 22:14:43 | Re: CallableStatements: index starts at 2 |
Previous Message | Kris Jurka | 2005-12-15 21:42:14 | Re: an efficient way of checking if the connection to a db |