Mark Drilling created TEIIDDES-1654: --------------------------------------- Summary: DDL Importer needs to better handle constraint naming in generated model Key: TEIIDDES-1654 URL: https://issues.jboss.org/browse/TEIIDDES-1654 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 8.1 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.2 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira