[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer
[
https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1010:
----------------------------------------
The fix treats unnamed Primary Keys by naming them PRIMARY_KEY. The Unique Index would
therefore ALSO be unnamed, so Designer will create an index for each named UNIQUE_IDX
prepended by a unique sequencial integer.
In the case of the SmallA and SmallB indexes from Van's example, Designer creates:
* SmallA index: UNIQUE_IDX
** Name in source:"dbo"."SmallA"."UNIQUE_IDX"
* SmallB index: UNIQUE_IDX
** Name in source:"dbo"."SmallB"."UNIQUE_IDX"
Note that the Name In Source holds the path reference to the corresponding target table.
Indexes are not qualified when imported with Teiid Designer
-----------------------------------------------------------
Key: TEIIDDES-1010
URL: https://issues.jboss.org/browse/TEIIDDES-1010
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.4
Reporter: Marc Shirley
Assignee: Barry LaFond
Fix For: 8.1
Attachments: org.teiid.designer.jdbc.relational.patch
Having multiple indexes with the same name (for example, 'PrimaryKey') imported
results in a conflict or merging of the indexes. This generates messages complaining of
an index referring to multiple tables in the Teiid Designer perspective. The indexes
should be qualified in order to remain unique or generated as a child of the associated
table in order to avoid these messages.
--
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