db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: ResultSet.getConcurrency() behaves differently on client and embedded
Date Sat, 25 Feb 2006 22:26:40 GMT
"Lance J. Andersen" <Lance.Andersen@Sun.COM> writes:

> We clarified this in JDBC 4 spec
> 
> 
> Once a ResultSet has been closed, any attempt to access any of its
> methods with
> the exception of the isClosed method will result in a SQLException being
> thrown. ResultSetMetaData instances that were created by a ResultSet that
> has been closed are still accessible.

Thanks, Lance! I'll go through all the ResultSet methods and file a
JIRA.

Does the same apply for Statement? I didn't see a similar comment
about Statement objects in the spec.

-- 
Knut Anders


Mime
View raw message