db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1464) runtimestatistics can show that an index is being used even when it isn't
Date Mon, 03 Jul 2006 02:40:32 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1464?page=all ]
Kathey Marsden resolved DERBY-1464:

    Fix Version:
     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 but there is no such version in Jira so marked it

> 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:
>     Reporter: Kathey Marsden
>     Assignee: Manish Khettry
>     Priority: Minor
>      Fix For:

> 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:
For more information on JIRA, see:

View raw message