You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/03/24 22:35:53 UTC

[jira] Commented: (DERBY-3955) test lang/selectivity.sql can be revived

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

Kathey Marsden commented on DERBY-3955:
---------------------------------------

Thanks Mike, that is very helpful.  If I do a full scan of both tables before running the query in the case where I create the index before inserting the data, I get the expected estimated row count (at least on trunk. Haven't tried elsewhere).  I agree that it makes sense for update statistics to update this store statistic as well. I'll file a Jira issue for that.


> test lang/selectivity.sql can be revived
> ----------------------------------------
>
>                 Key: DERBY-3955
>                 URL: https://issues.apache.org/jira/browse/DERBY-3955
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Myrna van Lunteren
>            Assignee: Kathey Marsden
>            Priority: Minor
>         Attachments: DERBY-3955.diff1, derby-3955_sanityCheck_dont_commit_diff.txt, oldSelectivity.java
>
>
> One test that was contributed during the IBM contribution of derby code was not runnable at the time - lang/selectivity.sql.
> This test is still there, and I think might have some valuable regression tests if it gets adapted to the current functionality in Derby.
> Ideally too, it should get converted to junit, or at least be made to run through the langScripts junit suite.

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