db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shreyas Kaushik (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
Date Thu, 23 Dec 2004 10:16:09 GMT
     [ http://nagoya.apache.org/jira/browse/DERBY-66?page=comments#action_57008 ]
     
Shreyas Kaushik commented on DERBY-66:
--------------------------------------

I think it's the other way around. As the JDBC api says "Retrieves whether this database supports
keeping cursors open across commits" it is the property of the database.

Since Derby can have cursors that are open across commits it should return true. 

To be even precise, when creating a ResultSet handle that needs to have cursors open across
commits, a check on whether the underlying Database supports such a holdability has to be
checked.

> 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