[
https://issues.apache.org/jira/browse/DERBY-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-910:
--------------------------------
Issue & fix info: [Repro attached]
Urgency: Normal
Triaged for 10.5.3: assigned normal urgency and noted that a repro is attached.
> RunTimeStatistics shows system generated backing index name rather than the
> constraint name when optimizer overrides is used for constraint
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-910
> URL: https://issues.apache.org/jira/browse/DERBY-910
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.2.1.6
> Reporter: Mamta A. Satoor
> Priority: Minor
>
> 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(i) references prim(i), 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
