[jira] Commented: (DERBY-3686) convert predicatePushdown.sql to JUnit

["Dag H. Wanvik (JIRA)" <ji...@apache.org>]

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

Dag H. Wanvik commented on DERBY-3686:
--------------------------------------

My 0.02 cents:
Might be good to add a comment on the use of findString that the magic number 4
refers back to the fact that there should be scalar qualifiers for all 4 scans.

The SQL is reformatted to be less readable in the JUnit version making it a lot harder to read than the original
which seems a bit of a loss.

It would be nice if the statistics output was more well defined and parsable. The current 
format is inherently brittle it seems... There may be a JIRA for this already; I didn't find one..


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