Uploaded image for project: 'Teiid Designer'
  1. Teiid Designer
  2. TEIIDDES-1654

DDL Importer needs to better handle constraint naming in generated model

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 8.2
    • 8.1
    • Import/Export
    • None

      When importing DDL, the generated model can have errors when multiple constraints are present. For example the following DDL:

      CREATE FOREIGN TABLE G1( e1 integer, e2 varchar, e3 date, PRIMARY KEY (e1, e2), INDEX(e2, e3), ACCESSPATTERN(e1), UNIQUE(e1), ACCESSPATTERN(e2, e3))

      includes two access patterns which end up being named the same. The importer should auto increment the names to avoid name conflicts.

              mdrillin1@redhat.com Mark Drilling (Inactive)
              mdrillin1@redhat.com Mark Drilling (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: