Bug 1267538 - Wrong Foreign Key reference when exporting Dynamic VDB
Summary: Wrong Foreign Key reference when exporting Dynamic VDB
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Barry LaFond
QA Contact: Andrej Smigala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-30 11:03 UTC by Andrej Smigala
Modified: 2015-11-17 18:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-17 18:06:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
project (25.88 KB, application/zip)
2015-09-30 11:03 UTC, Andrej Smigala
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDES-2672 0 Major Closed Wrong Foreign Key reference when exporting Dynamic VDB 2015-10-20 12:20:45 UTC

Description Andrej Smigala 2015-09-30 11:03:58 UTC
Created attachment 1078592 [details]
project

When creating a dynamic VDB from an existing VDB, Foreign Key definitions use the wrong table in the REFERENCES clause. The reference table is the same as the one that contains this FK.
For example, in the table SUPPLIER_PARTS, the following constraint is generated:

CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER_PARTS(SUPPLIER_ID)

which is obviously wrong. The correct constrant definition should be:

CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER(SUPPLIER_ID)


Steps to Reproduce:
# import the attached project
# right click the vdb, select Modeling -> Generate Dynamic VDB
# click Next, click Generate
# find the DDL for table SUPPLIER_PARTS, notice the FOREIGN KEY definitions

Comment 2 JBoss JIRA Server 2015-09-30 15:20:53 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-2672 to Resolved

Comment 3 JBoss JIRA Server 2015-10-20 07:14:45 UTC
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2672 to Closed


Note You need to log in before you can comment on or make changes to this bug.