db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3686) convert predicatePushdown.sql to JUnit
Date Thu, 29 May 2008 20:45:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kathey Marsden updated DERBY-3686:

    Attachment: derby-3686_complete_diff.txt

Here is a new patch derby-3686_complete_diff.txt  that replaces the previous one.  For check
for the four qualifiers I added  findString method to RuntimeStatisticsParser that takes a
number of instances to search for the string and called.
  p.findString("Operator: <=", 4);

Hopefully that is a sufficient check.
This patch also removes the old test and adds the new one to the lang._Suite.

Please review.

> 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:
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>         Attachments: derby-3686_complete_diff.txt, derby-3686_initial_conv_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.

View raw message