[ http://issues.apache.org/jira/browse/DERBY-1464?page=all ]
Kathey Marsden resolved DERBY-1464:
-----------------------------------
Fix Version: 10.2.0.0
Resolution: Fixed
Submitted to trunk with DERBY-578 patch.
Date: Sun Jul 2 19:37:42 2006
New Revision: 418672
URL: http://svn.apache.org/viewvc?rev=418672&view=rev
It is actually fixed in 10.2.0.4 but there is no such version in Jira so marked
it 10.2.0.0
> runtimestatistics can show that an index is being used even when it isn't
> -------------------------------------------------------------------------
>
> Key: DERBY-1464
> URL: http://issues.apache.org/jira/browse/DERBY-1464
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.5
> Reporter: Kathey Marsden
> Assignee: Manish Khettry
> Priority: Minor
> Fix For: 10.2.0.0
>
> The patch for DERBY-578 also fixes an issue that runtimestatistics may
> print that an index is being used, even when it isn't. Here is the
> explanation from DERBY-578.
> Earlier, we would set the indexName field in DistinctScanResult to the
> conglomerate name (cd.getName()) used to scan the table. If the conglomerate
> was the base table itself then this was just plain wrong. The change, for
> this patch, passes null if no index is being used.
> This bug should be marked fixed when DERBY-578 is checked in.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
