PostgreSQL JDBC - Change in parameters' order in prepared statement??

Author

Change in parameters' order in prepared statement??

Andres Olarte

2005-09-02, 8:24 pm

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?

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly

Oliver Jowett

2005-09-02, 8:24 pm

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

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Oliver Jowett

2005-09-04, 3:24 am

Oliver Jowett wrote:
> Andres Olarte wrote:
>
>
>
> This sounds like a bug -- can you provide a more detailed testcase?

Per off-list discussion this seems to be a bug that affects non-{call}
queries prepared via prepareCall() only; if prepareStatement() is used,
it works fine. I haven't dug deeper, but perhaps this is a bug
introduced by the OUT parameter support.

-O

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Sponsored Links