Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-140

Unique constrainsts should be checked in costing logic

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Optional
    • Resolution: Rejected
    • Affects Version/s: 9.x
    • Fix Version/s: 9.x
    • Component/s: Query Engine
    • Labels:
      None

      Description

      Defect Tracker #24750: Currently we only check primary key constraints in costing, however we should more generically check for uniqueness constraints.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                shawkins Steven Hawkins
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: