Re: Change in parameters' order in prepared statement??

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Andres Olarte <olarte(dot)andres(at)gmail(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Change in parameters' order in prepared statement??
Date: 2005-09-02 22:45:54
Message-ID: 4318D622.9030007@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Andres Olarte wrote:
> I recently updated the driver to the latest CVS version, and found a
> change in the way parameters are handled. Before, the first parameter
> was 1, as in:
>
> update.setInt(1,cbid);
>
> But now it's 2, as in:
>
> update.setInt(2,cbid);
>
> I'm using only IN parameters to call a prepared SELECT. Is this the
> correct behaviour? Is it going to stay this way?

This sounds like a bug -- can you provide a more detailed testcase?

-O

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2005-09-04 05:44:43 Re: Change in parameters' order in prepared statement??
Previous Message Andres Olarte 2005-09-02 22:33:57 Change in parameters' order in prepared statement??