[
https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1010:
----------------------------------------
A few things going on here.
1) Most legacy MM test DB tables with indexes use the "PK_<table name>"
convention so name conflicts were pretty much non existent
2) The "ExcelModelProcessor" is the only class that actually implements the
"modifyIndexName( IndexSpec indexSpec )" method for RelationalModelProcessorImpl
and it looks for indexes named "PrimaryKey" and converts to a name that appends
referenced column names
3) We need to create/add some test data that covers the "Multiple Schema"
use-case as well as a Set of Tables that use duplicate primary key names across tables
(i.e. use "PrimaryKey")
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
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira