Skip site navigation (1) Skip section navigation (2)

Re: Multiple open ResultSets not allowed?

From: Barry Lind <blind(at)xythos(dot)com>
To: Jeff Kolesky <jeff(at)edusoft(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Multiple open ResultSets not allowed?
Date: 2003-03-15 03:55:53
Message-ID: 3E72A449.1090006@xythos.com (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-jdbc
The error message says that the Connection is closed.  You can't use a 
statement or result set after the connection that owns them is closed. 
This is part of the jdbc spec, and I think logic in the driver was 
tightened up in this area in 7.3.

thanks,
--Barry


Jeff Kolesky wrote:
> I have just switched to using the 7.3 JDBC driver and am no longer 
> allowed to have multiple ResultSets open at the same time.
> 
> When running code that iterates through two open ResultSets (from two 
> different Statements from the same Connection), the following exception 
> is thrown:
> 
>     Connection is closed. Operation is not permitted.
>         at org.postgresql.jdbc1.AbstractJdbc1ResultSet.next
> (AbstractJdbc1ResultSet.java:92)
> 
> I haven't looked at the AbstractJdbc1ResultSet code to see what is going 
> on, but according to the JDBC Javadocs, "if the reading of one ResultSet 
> object is interleaved with the reading of another, each must have been 
> generated by different Statement objects."  Therefore, the code I am 
> executing should not throw this exception, and with the previous version 
> of the driver it did not.
> 
> Is this a known bug?  Has it been fixed?  Did I misinterpret the Javadocs?
> 
> Thanks.
> 
> Jeff
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
> 




In response to

Responses

pgsql-jdbc by date

Next:From: Barry LindDate: 2003-03-15 04:02:53
Subject: Re: idle in transaction
Previous:From: Jeff KoleskyDate: 2003-03-15 00:20:26
Subject: Multiple open ResultSets not allowed?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group