db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3304) Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable
Date Thu, 07 Feb 2008 05:57:11 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566453#action_12566453
] 

Mamta A. Satoor commented on DERBY-3304:
----------------------------------------

After re-reading Dan's comment about update conglomerate clearing, I think Dan is suggesting
that we leave the update conglomerate clearing code as it is for now and tackle that as a
separate jira entry. Based on this and other comments, I have just commited changes into trunk
which will take care of removing the clear warning code in the commit code path, fix the javadoc
for resetActivations, rename resetActivations and remove the holdability false setting for
activations at the time rollback code path. These changes went in as revision 619279. I will
merge 619279 and 618788 into 10.3 codeline. I will also see if I can add some more testing
for these changes.

> Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3304
>                 URL: https://issues.apache.org/jira/browse/DERBY-3304
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.4.0.0
>            Reporter: Daniel John Debrunner
>            Assignee: Mamta A. Satoor
>         Attachments: Main.java
>
>
> Repro (Main.java) that shows changed behavior after svn 602991
> (the patch committed for this issue). It seems a regression: (originally from Dag H.
Wanvik attached to DERBY-1585)
> An explicit commit inside a stored procedure makes a dynamic result sets passed out unavailable,
even if the commit is executed *prior* to the result set; as in the repro.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message