[DERBY-910] RunTimeStatistics shows system generated backing index name rather than the constraint name when optimizer overrides is used for constraint

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.2.1.6
• Component/s: SQL
• Labels: derby_triage10_5_2
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Mamta A. Satoor
• Created: 02/Feb/06 04:03
• Updated: 15/Feb/11 21:08

Description

When user specifies a constraint name in optimizer overrides for a query, the runtime statistics info on that query shows the backing index name rather than the constraint name. eg
create table prim ( i int not null primary key, j int);
create table sec (i int, constraint fk foreign key references prim, j int);

select * from sec --derby-properties constraint=fk
;

...........................................
optimizer estimated cost: 136.34

User supplied optimizer overrides on SEC are

{ index=SQL060131012414010}

<=========
Index Scan ResultSet for SEC using constraint FK at read committed isolation level using instantaneous share row locking chosen by the optimizer
Number of opens = 1