[DERBY-1060] ResultSet methods should throw exception when the ResultSet is closed

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: JDBC, Network Client
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 27/Feb/06 22:45
• Updated: 29/Jun/09 13:13
• Resolved: 06/Mar/06 14:45

Description

The JDBC 4 spec says:

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.

This is not always the case in Derby, and the behaviour is not the
same on the client driver and the embedded driver.

The following ResultSet methods do not throw an exception when the
result set is closed:

Client driver:

clearWarnings()
close()
getMetaData()
getStatement()
getWarnings()

Embedded driver:

close()
getConcurrency()
getRow()
getStatement()
getType()
rowDeleted()
rowInserted()
rowUpdated()
setFetchDirection()
getFetchDirection()
setFetchSize()
getFetchSize()