db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-4378) Create test cases for MultiProbeTableScanResultSet with duplicates in the probe list
Date Fri, 26 Jul 2013 08:31:50 GMT

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

Knut Anders Hatlen resolved DERBY-4378.
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.11.0.0
    Issue & fix info:   (was: Patch Available)
    
> 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
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.11.0.0
>
>         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

Mime
View raw message