db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Reopened: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return true.
Date Mon, 31 Jan 2005 06:34:17 GMT
     [ http://issues.apache.org/jira/browse/DERBY-66?page=history ]
     
Mamta A. Satoor reopened DERBY-66:
----------------------------------


I think the patch for this bug is incorrect because Derby doesn't support open cursors across
commits for XA transactions. This might have been the reason why DatabaseMetaData.supportsOpenCursorsAcrossCommit
was returning false prior to the submitted patch. I will submit a new patch which will have
DatabaseMetaData.supportsOpenCursorsAcrossCommit return false.

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

>
> 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://issues.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