Calling ResultSet.close() a second time will be a no-op and this will be updated for the PFD of JDBC 4

-lance

Knut Anders Hatlen (JIRA) wrote:
     [ http://issues.apache.org/jira/browse/DERBY-1060?page=all ]

Knut Anders Hatlen reassigned DERBY-1060:
-----------------------------------------

    Assign To: Knut Anders Hatlen

  
ResultSet methods should throw exception when the ResultSet is closed
---------------------------------------------------------------------

         Key: DERBY-1060
         URL: http://issues.apache.org/jira/browse/DERBY-1060
     Project: Derby
        Type: Bug
  Components: JDBC, Network Client, Newcomer
    Versions: 10.2.0.0
    Reporter: Knut Anders Hatlen
    Assignee: Knut Anders Hatlen
    Priority: Minor
    

  
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()