db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen" <Bernt.John...@Sun.COM>
Subject Re: [jira] Created: (DERBY-545) Should ResultSet Close implicitly?
Date Tue, 30 Aug 2005 15:26:56 GMT
>>>>>>>>>>>> Philip Wilder (JIRA) wrote (2005-08-30 14:22:07):
> Should ResultSet Close implicitly?
> ----------------------------------
> 
>          Key: DERBY-545
>          URL: http://issues.apache.org/jira/browse/DERBY-545
>      Project: Derby
>         Type: Improvement
>   Components: JDBC  
>     Versions: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.2.0.0, 10.1.1.1    
>  Reporter: Philip Wilder
>     Priority: Minor
> 
> 
> While work on DERBY-213 has resulted in a client ResultSet that matches the functionality
of embedded ResultSet it is possible that both embedded and client are now wrong.
> 
> According to the JDBC 3.0 specification:
> 
> "For Select statements, the statement is complete when the associated result set is 
> closed. The result set is closed as soon as one of the following occurs: 
> - all of the rows have been retrieved"
> 
> At the moment ResultSets will only close implicitly if holdability
> is set to CLOSE_CURSORS_AT_COMMIT.

Implict close should also apply only to TYPE_FORWARD_ONLY. 


-- 
Bernt Marius Johnsen, Database Technology Group, 
Sun Microsystems, Trondheim, Norway

Mime
View raw message