db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-910) RunTimeStatistics shows system generated backing index name rather than the constraint name when optimizer overrides is used for constraint
Date Wed, 01 Feb 2006 19:04:03 GMT
RunTimeStatistics shows system generated backing index name rather than the constraint name
when optimizer overrides is used for constraint
-------------------------------------------------------------------------------------------------------------------------------------------

         Key: DERBY-910
         URL: http://issues.apache.org/jira/browse/DERBY-910
     Project: Derby
        Type: Bug
  Components: SQL  
    Versions: 10.2.0.0    
    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.
-
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


Mime
View raw message