db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Craven (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
Date Fri, 12 Nov 2004 10:34:26 GMT
     [ http://nagoya.apache.org/jira/browse/DERBY-66?page=comments#action_55394 ]
     
Jon Craven commented on DERBY-66:
---------------------------------

What's the difference between open cursors across commits and holding cursors across commit?
 Derby clearly supports the latter, supportsResultSetHoldability() returns true and HOLD_CURSORS_OVER_COMMIT
is the default holdability.

> Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit
return true.
> -----------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-66
>          URL: http://nagoya.apache.org/jira/browse/DERBY-66
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions: 10.0.2.0
>     Reporter: Mamta A. Satoor
>     Priority: Minor

>
> Derby returns false for DatabaseMetaData.supportsOpenCursorsAcrossCommit. But that seems
incorrect because Derby does support open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit
return true.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message