Bug 780725

Summary:	Indexes are not qualified when imported with Teiid Designer
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Marc Shirley <mshirley>
Component:	Tooling	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	soa-p-jira, vhalbert
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-3179
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	SOA-3179	Environment:
Last Closed:	2012-07-18 13:08:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marc Shirley 2011-07-15 15:01:56 UTC

++ 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.

Comment 1 Van Halbert 2011-07-15 15:01:57 UTC

Link: Added: This issue Cloned from TEIIDDES-1010

Comment 2 Van Halbert 2011-07-15 15:03:00 UTC

Security: Added: Public

Comment 3 Van Halbert 2012-01-24 13:55:14 UTC

Teiid Designer has targeted this to its 8.0 release

Comment 4 Van Halbert 2012-02-06 15:24:25 UTC

Retargeted to SOA 6 because Teiid Designer has indicated thats when this will be fixed.

Comment 5 Van Halbert 2012-07-18 13:08:14 UTC


*** This bug has been marked as a duplicate of bug 780724 ***

Comment 6 JBoss JIRA Server 2012-11-08 17:50:43 UTC

Van Halbert <vhalbert> made a comment on jira TEIIDDES-1010

Are you considering fixing this for 8.x?

Comment 7 JBoss JIRA Server 2013-01-25 20:06:11 UTC

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

Comment 10 JBoss JIRA Server 2013-02-07 19:45:56 UTC

Barry LaFond <blafond> updated the status of jira TEIIDDES-1010 to Resolved

Comment 11 JBoss JIRA Server 2013-02-07 19:45:56 UTC

Barry LaFond <blafond> made a comment on jira TEIIDDES-1010

Done

Comment 12 JBoss JIRA Server 2013-02-28 16:40:50 UTC

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.

Comment 13 JBoss JIRA Server 2013-04-29 16:05:36 UTC

Barry LaFond <blafond> updated the status of jira TEIIDDES-1010 to Closed