Derby
  1. Derby
  2. DERBY-910

RunTimeStatistics shows system generated backing index name rather than the constraint name when optimizer overrides is used for constraint

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: None
    • Component/s: SQL
    • Urgency:
      Normal
    • Issue & fix info:
      Repro attached

      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

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Mamta A. Satoor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development