db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4318) convert inbetween.sql to JUNIT
Date Sat, 01 Aug 2009 15:31:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737893#action_12737893

Bryan Pendleton commented on DERBY-4318:

Hi Eranda, Actually, as I look at the test more closely, I think it
would be easier to use the XPLAIN tables feature instead of the
RuntimeStatisticsParser to do these sections of the test.

But first, let's figure out the problem with the consistency checker
and the wrong number of dependencies; then we can go back and work on
changing the query plan verification in the test to use XPLAIN table checking.

I'm wondering if the dependencies problem has to do with this comment in inbetween_derby.properties:

-# wants to do consistency checking, so needs
-# the statement cache off to ensure no trailing dependencies exist

I think we should be able to use DatabasePropertyTestSetup here.

Can you try changing



"derby.language.statementCacheSize", "0"));

to see if this has any effect on the dependencies that the ConsistencyChecker finds?

> convert inbetween.sql to JUNIT
> ------------------------------
>                 Key: DERBY-4318
>                 URL: https://issues.apache.org/jira/browse/DERBY-4318
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Eranda Sooriyabandara
>            Assignee: Eranda Sooriyabandara
>            Priority: Minor
>         Attachments: inbetween.junit, InbetweenTest.diff, InbetweenTest.diff
> conversion of inbetween.sql to JUNIT

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

View raw message