From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Andres Olarte <olarte(dot)andres(at)gmail(dot)com> |
Cc: | Thomas Frieling <frieling(at)8hertz(dot)de>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: CallableStatements: index starts at 2 |
Date: | 2005-12-14 17:41:58 |
Message-ID: | C28DF2D1-AD42-47E3-9324-35E2F7014019@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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.
dave
On 14-Dec-05, at 11:38 AM, Andres Olarte wrote:
> You probably should use prepareStatement instead of prepareCall. I
> had the same problem. You can search the archives to look for a
> better explanation which I don't remmember right now
>
> On 12/14/05, Thomas Frieling <frieling(at)8hertz(dot)de> wrote:
> It seems that in Version "8.2dev-500 JDBC 3" CallableStatements are
> implemented differently from older Versions.
> The index to set fields now starts at 2.
>
> This _did_ work:
> CallableStatement cS = con.prepareCall("{ call test(?)}";
> cS.setString( 1, "abc" );
>
> This _now_ works:
> CallableStatement cS = con.prepareCall("{ call test(?)}";
> cS.setString( 2, "abc" );
>
> Thanks,
> Thomas
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that
> your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Assad Jarrahian | 2005-12-15 20:47:03 | an efficient way of checking if the connection to a db is actually open |
Previous Message | Andres Olarte | 2005-12-14 16:38:24 | Re: CallableStatements: index starts at 2 |