Bug 1009460 - Keys are not imported by default when using dynamic VDB
Summary: Keys are not imported by default when using dynamic VDB
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER3
: 6.0
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-18 13:50 UTC by Filip Elias
Modified: 2014-07-09 05:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-06 15:37:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-2667 0 Major Closed Keys are not imported by default when using dynamic VDB 2014-01-10 04:43:34 UTC

Description Filip Elias 2013-09-18 13:50:36 UTC
Primary and foreign keys are not imported by defaut when using dynamic VDB. 
According to the documentation they should be imported by default when using JDBC translator.

Comment 1 JBoss JIRA Server 2013-09-18 15:57:01 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2667

It looks like several of the documented properties do not match the defaults:

importIndexes, importKeys, importProcedures

and

autoCreateUniqueConstraints is also missing from the doc page (added with TEIID-1946 and roughly corresponds to the designer option to import incomplete foreign keys).

I believe we at one point were trying to mimic Designer's defaults as much as it made sense.  At least having importProcedures/importIndexes defaulted as false is fine, so the doc should be changed for those.  Since we don't split importKeys into primary/unique vs. foreign, having it defaulted to false doesn't make much sense.  As long as autoCreateUniqueConstraints is true (the default) and given that we automatically ignore foreign keys to non-imported tables, then there's no chance that having importKeys set to true should result in invalid metadata.  We would just want to document the switch in the actual default as a compatibility change if for whatever reason someone was relying on the current behavior.

Comment 2 JBoss JIRA Server 2013-09-18 17:06:15 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-2667 to Resolved

Comment 3 JBoss JIRA Server 2013-09-18 17:06:15 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2667

Resolved for 8.6.  Let me know when it can be committed to 8.4.x

Comment 9 Filip Elias 2013-11-15 09:36:45 UTC
Verified on DV6 ER3

Comment 10 JBoss JIRA Server 2013-12-05 20:51:50 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-2667 to Closed


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