[
https://issues.apache.org/jira/browse/DERBY-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601157#action_12601157
]
Kathey Marsden commented on DERBY-3686:
---------------------------------------
Thanks Dag for looking at the test. I'll add the comment. As for the
reformatting of the sql, it seems to be a feature of the SQLToJUnit utility.
perhaps that utility could be changed to keep existing line breaks if they are
short enough to fit in the line. I don't think I'll go back and redo the whole
test now, but it sounds like a good improvement for the tool. There is also a
problem with the tool that it will not put in line breaks after single line
comments. This might fix that problem too. I'll take a look and see if it is
easy to do.
I don't think there is an issue for making the statistics easier to parse. If
you have some ideas in this regard, please file an issue.
> convert predicatePushdown.sql to JUnit
> ---------------------------------------
>
> Key: DERBY-3686
> URL: https://issues.apache.org/jira/browse/DERBY-3686
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3686_complete_diff.txt,
> derby-3686_initial_conv_diff.txt, derby-3686_rts_diff.txt
>
>
> predicatePushdown.sql fails intermittently in the nightlies ( DERBY-1902)
> with a plan variance. It would be good to convert it to JUnit and extract
> only the relevant information from RuntimeStatistics output. This might make
> the test more stable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
