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. > > > >
