Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <689504850.1141048009458.JavaMail.jira@ajax.apache.org>
Date: Mon, 27 Feb 2006 14:46:49 +0100 (CET)
From: "Knut Anders Hatlen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-1060) ResultSet methods should throw
 exception when the ResultSet is closed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira