[
https://issues.apache.org/jira/browse/DERBY-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-3955.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.11.0.0
It looks as if the instability has been addressed now, the latest test runs at
Oracle seem clear, and where reasonable checks to see if the optimizer picks
expected paths have been added. I do not intend to add to this test at this
time, so resolving.
> test lang/selectivity.sql can be revived
> ----------------------------------------
>
> Key: DERBY-3955
> URL: https://issues.apache.org/jira/browse/DERBY-3955
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.11.0.0
>
> Attachments: DERBY-3955.diff1, DERBY-3955.diff2, DERBY-3955.diff3,
> DERBY-3955.diff4, 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 was sent by Atlassian JIRA
(v6.1.5#6160)
