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 "Mamta A. Satoor (JIRA)" <de...@db.apache.org> on 2005/01/19 02:09:17 UTC
[jira] Updated: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return true.
[ http://issues.apache.org/jira/browse/DERBY-66?page=history ]
Mamta A. Satoor updated DERBY-66:
---------------------------------
Assign To: Mamta A. Satoor
Summary: Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return true. (was: Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.)
Fix Version: 10.0.2.1
> 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