db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4086) BTreeScan.isCurrentPositionDeleted() should return true if the row has been purged
Date Thu, 02 Jul 2009 19:09:47 GMT

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

Rick Hillegas updated DERBY-4086:
---------------------------------

    Urgency: Normal

Triaged July 2, 2009: Assigned normal urgency.

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message