db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2953) Dump the information about rollbacks of the global transaction (introduced in DERBY-2220 and DERBY-2432) to derby.log
Date Mon, 05 Nov 2007 13:56:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540195
] 

Dyre Tjeldvoll commented on DERBY-2953:
---------------------------------------

Hi Julio,

I could still apply the patch, and both test suites ran successfully for me. Overall the patch
looks good. I'm just a bit curious about why some of the new methods have javadoc and some
do not. Some have a good description that is not valid javadoc (e.g. without any tags). Was
this intentional? I'm never sure when javadoc is required and when it is optional. 

> Dump the information about rollbacks of the global transaction (introduced in DERBY-2220
and DERBY-2432) to derby.log
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2953
>                 URL: https://issues.apache.org/jira/browse/DERBY-2953
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>            Reporter: Julius Stroffek
>            Assignee: Julius Stroffek
>             Fix For: 10.3.1.4, 10.4.0.0
>
>         Attachments: d2953.diff, d2953.stat
>
>
> When the global transaction is going to be rolled back that information should be dumped
to derby.log so that users can find out what happened.

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