Postgres Pro
Downloads
Home   >   mailing lists

Thread: Result set not positioned properly, perhaps you need to call next().

Result set not positioned properly, perhaps you need to call next().

From
Manuel Sugawara
Date:
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?.

Regards,
Manuel.

Re: Result set not positioned properly, perhaps you need to

From
Oliver Jowett
Date:
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

Re: Result set not positioned properly, perhaps you need to

From
Manuel Sugawara
Date:
Oliver Jowett <oliver@opencloud.com> writes:

> 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.

Never mind. I found the problem in my code, I was calling getString()
after next() returned false. Sorry for the noise.

Regards,
Manuel.