++ This bug is a clone of bug 780724 ++ Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007C5ML project_key: SOA 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.
Link: Added: This issue Cloned from TEIIDDES-1010
Security: Added: Public
Teiid Designer has targeted this to its 8.0 release
Retargeted to SOA 6 because Teiid Designer has indicated thats when this will be fixed.
*** This bug has been marked as a duplicate of bug 780724 ***
Van Halbert <vhalbert> made a comment on jira TEIIDDES-1010 Are you considering fixing this for 8.x?
Barry LaFond <blafond> made a comment on jira TEIIDDES-1010 Van, could you find/set up on one of our testing boxes a Schema that will return multiple tables/indexes where the PK is unnamed so I can use it to test/fix this? thx
Barry LaFond <blafond> updated the status of jira TEIIDDES-1010 to Resolved
Barry LaFond <blafond> made a comment on jira TEIIDDES-1010 Done
Barry LaFond <blafond> made a comment on jira 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.
Barry LaFond <blafond> updated the status of jira TEIIDDES-1010 to Closed