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 "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/03/01 13:49:43 UTC
[jira] Assigned: (DERBY-1060) ResultSet methods should throw
exception when the ResultSet is closed
[ 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()
--
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
Re: [jira] Assigned: (DERBY-1060) ResultSet methods should throw
exception when the ResultSet is closed
Posted by "Lance J. Andersen" <La...@Sun.COM>.
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()
>>
>
>