Re: Result set not positioned properly, perhaps you need to - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: Result set not positioned properly, perhaps you need to
Date
Msg-id 41A667EF.7010406@opencloud.com
Whole thread Raw
In response to Result set not positioned properly, perhaps you need to call next().  (Manuel Sugawara <masm@fciencias.unam.mx>)
Responses Re: Result set not positioned properly, perhaps you need to
List pgsql-jdbc
Manuel Sugawara wrote:
> I have a system which have been up for years now and recently when
> switched to pg74.215.jdbc3.jar it started to fail saying:
>
> org.postgresql.util.PSQLException: Result set not positioned properly, perhaps you need to call next().
>         at org.postgresql.jdbc1.AbstractJdbc1ResultSet.checkResultSet(AbstractJdbc1ResultSet.java:823)
>         at org.postgresql.jdbc1.AbstractJdbc1ResultSet.getString(AbstractJdbc1ResultSet.java:200)
>         at org.postgresql.jdbc1.AbstractJdbc1ResultSet.getString(AbstractJdbc1ResultSet.java:480)
>         at org.apache.commons.dbcp.DelegatingResultSet.getString(DelegatingResultSet.java:155)
>         ....
>
> The funny thing is that switching back to pg74.214.jdbc3.jar solves
> the problem. Is this a know bug?.

Can you show us the application code that causes this? It may be an
application bug that was hidden by the old driver's behaviour. Newer
drivers tend to be more aggressive about checking resultset positioning,
enforcing spec requirements, etc.

-O

pgsql-jdbc by date:

Previous
From: Manuel Sugawara
Date:
Subject: Result set not positioned properly, perhaps you need to call next().
Next
From: "Éric Paré"
Date:
Subject: using index with bigint pkey