[jira] [Updated] (DERBY-4086) BTreeScan.isCurrentPositionDeleted() should return true if the row has been purged

["Mike Matrigali (Updated) (JIRA)" <ji...@apache.org>]

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

Mike Matrigali updated DERBY-4086:
----------------------------------

    Labels: derby_triage10_5_2 derby_triage10_9  (was: derby_triage10_5_2)

Triaged for 10.9, no changes.
                
> BTreeScan.isCurrentPositionDeleted() should return true if the row has been purged
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-4086
>                 URL: https://issues.apache.org/jira/browse/DERBY-4086
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.4.2.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>              Labels: derby_triage10_5_2, derby_triage10_9
>
> Currently, BTreeScan.isCurrentPositionDeleted() returns false if the current position has been purged (that is, if reposition(scan_position, false) returns false). Since a row must be deleted in order to be purged, I believe it is more correct if isCurrentPositionDeleted() returns true in this case.
> (I'm not sure if it is possible to exercise this code path in the current code. It is not exercised by any of the existing regression tests. Its only caller, TableScanResultSet.getCurrentRow(), also calls doesCurrentPositionQualify() which correctly returns false in this case, and it therefore skips the row and hides this problem. So even if the code can be exercised, it shouldn't cause any observable problems at this time.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira