You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2013/06/25 17:04:20 UTC
[jira] [Updated] (DERBY-884) allow and use backward scans on
indexes.
[ https://issues.apache.org/jira/browse/DERBY-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor updated DERBY-884:
----------------------------------
Urgency: Low
Labels: derby_triage10_11 (was: )
> allow and use backward scans on indexes.
> ----------------------------------------
>
> Key: DERBY-884
> URL: https://issues.apache.org/jira/browse/DERBY-884
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Store
> Affects Versions: 10.1.3.1
> Reporter: Mike Matrigali
> Priority: Minor
> Labels: derby_triage10_11
>
> Improve the access interface to support backward scans, currently only forward scans are supported.
> Improve the btree implementation to support backward scans. The structure could support this, the work just has not been done. With
> row level locking, concurrent tree splitting, and current assumptions
> throughout the access method that scans go top/down, left to right the
> work to do a backward scan is harder than doing a forward scan. Also
> once the store portion is done, there would be necessary changes to:
> optimizer, execution engine, and scan interface to allow the backward
> scan. This would be a hard first project.
> Improve the optimizer to understand derby indexes now support backward scans.
> Improve the execution engine to use the new backward scan interfaces to execute backward scans.
--
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