[
https://issues.apache.org/jira/browse/DERBY-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4378:
--------------------------------------
Attachment: d4378-1a.diff
Attaching a test case that adds the suggested test case. I ran
InListMultiProbeTest with JaCoCo and verified that the previously missed lines
were now covered. The only code in MultiProbeTableScanResultSet that's not
covered after the patch, is the xplain-only mode short-circuiting in
getNextRowCore().
> Create test cases for MultiProbeTableScanResultSet with duplicates in the
> probe list
> ------------------------------------------------------------------------------------
>
> Key: DERBY-4378
> URL: https://issues.apache.org/jira/browse/DERBY-4378
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.6.1.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Attachments: d4378-1a.diff
>
>
> See the coverage report for MultiProbeTableScanResultSet:
> http://dbtg.foundry.sun.com/derby/test/coverage/jvm1.6/sol/suitesAll82289/_files/401.html
> There are three red lines (lines that are not exercised by the tests).
> Adding a test case where the probe list contains duplicate values will
> exercise the first red line in getNextProbeValue().
> If the duplicates are also the last elements in the probe list, the other two
> red lines (in getNextProbeValue() and reopenScanController()) will be
> exercised too.
> Note that MultiProbeTableScanResultSet will sort the probe list, so the last
> element in the probe list is not necessarily identical to the last element in
> the query's IN list. It will also remove duplicates at compile time, if
> possible, so the IN list needs to contain parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
