Bug 780724 (SOA-3179) - Indexes are not qualified when imported with Teiid Designer
Summary: Indexes are not qualified when imported with Teiid Designer
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: SOA-3179
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER2
: 6.0
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
: 780725 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-15 15:01 UTC by Marc Shirley
Modified: 2014-07-09 05:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Importing multiple indexes with the same name (for example, 'PrimaryKey') resulted in a conflict or merging of the indexes. The user would receive messages alerting to an index referring to multiple tables in the Teiid Designer perspective. Unnamed Primary Keys are now dealt with by naming them PRIMARY_KEY. Since the Unique Index is also unnamed, Teiid Designer creates an index for each named UNIQUE_IDX prefixed with a unique sequential integer.
Clone Of:
: 780725 (view as bug list)
Environment:
Last Closed: 2014-02-06 15:36:48 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3179 0 Major Closed Indexes are not qualified when imported with Teiid Designer 2017-03-06 04:27:03 UTC
Red Hat Issue Tracker TEIIDDES-1010 0 Major Closed Indexes are not qualified when imported with Teiid Designer 2017-03-06 04:27:03 UTC

Description Marc Shirley 2011-07-15 15:01:56 UTC 
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-07-18 13:08:14 UTC 
*** Bug 780725 has been marked as a duplicate of this bug. ***
Comment 4 JBoss JIRA Server 2013-01-25 20:06:13 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 7 JBoss JIRA Server 2013-02-07 19:45:58 UTC 
Barry LaFond <blafond> updated the status of jira TEIIDDES-1010 to Resolved
Comment 8 JBoss JIRA Server 2013-02-07 19:45:58 UTC 
Barry LaFond <blafond> made a comment on jira TEIIDDES-1010

Done
Comment 9 JBoss JIRA Server 2013-02-28 16:40:48 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 10 JBoss JIRA Server 2013-04-29 16:05:38 UTC 
Barry LaFond <blafond> updated the status of jira TEIIDDES-1010 to Closed
Comment 14 belong 2013-11-19 23:29:09 UTC 
Fixed before GA - setting to requires_doc_text- accordingly
Comment 15 Lucie Fabrikova 2014-02-05 16:49:32 UTC 
Verified in JBDSIS-7.0.0.GA-GA + DV 6.0.0.GA.
Note You need to log in before you can comment on or make changes to this bug.