[DERBY-1464] runtimestatistics can show that an index is being used even when it isn't

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.1.3.1
• Fix Version/s: 10.2.1.6
• Component/s: SQL
• Assignee: Manish Khettry
• Reporter: Katherine Marsden
• Created: 29/Jun/06 20:07
• Updated: 02/May/13 02:29
• Resolved: 03/Jul/06 09:40

Description

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.

Issue Links

• depends upon: DERBY-578 Grouped select from temporary table raises null pointer exception in byte code generator