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 2004/11/11 08:43:23 UTC
[jira] Created: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
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
[jira] Updated: (DERBY-66) Derby does not support open cursor across commits for XA transactions and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return false.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-66?page=history ]
Mamta A. Satoor updated DERBY-66:
---------------------------------
Summary: Derby does not support open cursor across commits for XA transactions and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return false. (was: Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return true.)
> Derby does not support open cursor across commits for XA transactions and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return false.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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
[jira] Updated: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return true.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ 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
[PATCH] (DERBY-66) Derby does not support open cursor across commits for
XA transactions and hence
DatabaseMetaData.supportsOpenCursorsAcrossCommit should return false.
Posted by Mamta Satoor <ma...@Remulak.Net>.
Hi,
Can a commiter please commit the attached patch for Derby-66? The patch will have
DatabaseMetaData.supportsOpenCursorsAcrossCommit return false because Derby
does not support open cursors across commit for XA transactions. I have put a
comment in the code so we know why this method should return false.
thanks,
Mamta
[PATCH] (DERBY-66) Derby supports open cursor acrosscommits and hence
DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
Posted by Mamta Satoor <ma...@Remulak.Net>.
If the attached patch looks good, can one of the commiters commit it?
Mamta Satoor wrote:
>
> Here is a simple patch for the bug. Please review, comment/vote on it.
>
> thanks,
> Mamta
>
> > > Shreyas Kaushik (JIRA) wrote:
> > > > [ 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.
> > > >
> > > >
Re: [jira] Commented: (DERBY-66) Derby supports open cursor
acrosscommits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit
return true.
Posted by Mamta Satoor <ma...@Remulak.Net>.
Mamta Satoor wrote:
> Based on the discussion we have had on this bug, I will submit a patch which will return
> true for DatabaseMetaData.supportsOpenCursorsAcrossCommit.
>
> thanks,
> Mamta
>
> Shreyas Kaushik wrote:
>
> > Can someone please update what is happening on this issue?
> >
> > thanks
> > Shreyas
> >
> > Shreyas Kaushik (JIRA) wrote:
> > > [ 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.
> > >
> > >
Here is a simple patch for the bug. Please review, comment/vote on it.
thanks,
Mamta
Re: [jira] Commented: (DERBY-66) Derby supports open cursor
acrosscommits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit
return true.
Posted by Mamta Satoor <ma...@Remulak.Net>.
Based on the discussion we have had on this bug, I will submit a patch which will return
true for DatabaseMetaData.supportsOpenCursorsAcrossCommit.
thanks,
Mamta
Shreyas Kaushik wrote:
> Can someone please update what is happening on this issue?
>
> thanks
> Shreyas
>
> Shreyas Kaushik (JIRA) wrote:
> > [ 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.
> >
> >
Re: [jira] Commented: (DERBY-66) Derby supports open cursor across
commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
Posted by Shreyas Kaushik <Sh...@Sun.COM>.
Can someone please update what is happening on this issue?
thanks
Shreyas
Shreyas Kaushik (JIRA) wrote:
> [ 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.
>
>
[jira] Commented: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
Posted by "Shreyas Kaushik (JIRA)" <de...@db.apache.org>.
[ 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
Re: [jira] Commented: (DERBY-66) Derby supports open cursor across
commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit
return true.
Posted by Mamta Satoor <ma...@Remulak.Net>.
That is a good question.
I looked up in the bok JDBC API Tutorial and Reference, Third Edition.
On page 44 and it says following
"Result Sets and Cursors
The rows that satisfy the conditions of a query are called the
result set. A user can access the data in a result set one row
at a time, and a cursor provides the means to do that. A cursor
can be thought of as a pointer into a file that contains the rows
of the result set, and that pointer has the ability to keep track
of which row is currently being accessed........
Most DBMSs create a cursor automatically when a result
set in generated".
So, it looks there a fine line between a cursor and resultset.
Based on the information from the book, does it mean there
is 1 to 1 relationship between cursor and resultset and hence
if the database supports holdable resultset then that also
means cursors are held over commit?
Any comments/feedback from the Derby community on this.
Mamta
"Jon Craven (JIRA)" wrote:
> [ 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
[jira] Commented: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
Posted by "Jon Craven (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://nagoya.apache.org/jira/browse/DERBY-66?page=comments#action_56082 ]
Mamta A. Satoor commented on DERBY-66:
--------------------------------------
IMO, open cursors across commits and holding cursors across commits mean one and the same thing for Derby. But what is unclear to me is the description of return value of DatabaseMetaData.supportsOpenCursorsAcrossCommit in the JDBC api.
The JDBC api says following
boolean supportsOpenCursorsAcrossCommit() throws SQLExceptionRetrieves whether this database supports keeping cursors open across commits.
Returns:
true if cursors always remain open; false if they might not remain open
Throws:
SQLException - if a database access error occurs
A ResultSet object maintains a cursor pointing to its current row of data. Derby will keep the cursor open across commit if the ResultSet object's holdability is set to HOLD_CURSORS_OVER_COMMIT. If the ResultSet object's holdability is set to CLOSE_CURSORS_AT_COMMIT, the cursor will be closed when the transaction is committed. So, in Derby, whether a cursor stays open or closed across commit depends on the holdability of the ResultSet object. Does it then mean from the above api description that supportsOpenCursorsAcrossCommit() should return false in Derby?
If that is the conclusion, then there is no bug with current implementation of supportsOpenCursorsAcrossCommit().
> 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
[jira] Commented: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit return true.
Posted by "Shreyas Kaushik (JIRA)" <de...@db.apache.org>.
[ http://nagoya.apache.org/jira/browse/DERBY-66?page=comments#action_55667 ]
Shreyas Kaushik commented on DERBY-66:
--------------------------------------
Currently the supportsOpenCursorsAcrossCommits returns false, the fix for this is to make it return true? Can more explanation be provided for the previous comment?
> 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
[jira] Closed: (DERBY-66) Derby does not support open cursor across commits for XA transactions and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return false.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-66?page=history ]
Mamta A. Satoor closed DERBY-66:
--------------------------------
Resolution: Fixed
Fix Version: 10.1.0.0
(was: 10.0.2.1)
The patch for this was committed as revision 152678
> Derby does not support open cursor across commits for XA transactions and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return false.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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.1.0.0
>
> 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
[jira] Reopened: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return true.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Closed: (DERBY-66) Derby supports open cursor across commits and hence DatabaseMetaData.supportsOpenCursorsAcrossCommit should return true.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-66?page=history ]
Mamta A. Satoor closed DERBY-66:
--------------------------------
Resolution: Fixed
The fix for this went as svn commit: r125571
> 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