You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2008/02/25 07:42:51 UTC

[jira] Created: (DERBY-3459) Ensure that cleanup() puts the Language ResultSet objects in usable state in case an exception is raised

Ensure that cleanup() puts the Language ResultSet objects in usable state in case an exception is raised
--------------------------------------------------------------------------------------------------------

                 Key: DERBY-3459
                 URL: https://issues.apache.org/jira/browse/DERBY-3459
             Project: Derby
          Issue Type: Task
          Components: JDBC
    Affects Versions: 10.3.1.4, 10.4.0.0
            Reporter: Mamta A. Satoor


DERBY-827 made changes so that Language ResultSets do not get thrown away after every execution. 

But now that ResultSet gets used over and over, we need to make sure that in case of an exception, the ResultSet gets cleaned up properly for next execution. I noticed that we definitley do not do any cleanup for CallableStatementResultSet. The cleanup() method inside CallableStatementResultSet is empty. At the least, we should be calling close() method inside of cleanup() for CallableStatementResultSet. There might be other Language ResultSets that also require cleanup. I wonder if all the Language ResultSets can simply rely on the close() method to do whatever cleanup work that might be required during exception and we can probably simply get rid of cleanup() method. I haven't done enough investigation to know if that is the path we should go.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.