]
Steven Hawkins commented on TEIIDDES-971:
-----------------------------------------
With Teiid dynamic vdb metadata importing any fk key that is imported that does not have a
corresponding pk is simply ignored. I think Joel is getting at something similar here.
An import option such that if you specifically import only A, then any fk will be ignored
to a table that was not imported. Although you could just as easily manually delete the
fk from the table to achieve the same effect.
Teiid does expect fk entries to have a corresponding pk. There is little to no value at
runtime for having an fk without a pk. So if you change the validation, then don't
index invalid fks.
In Designer, when importing tables with foreign keys, let user bring
in tables without foreign key dependency errors / allow override
-------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-971
URL:
https://issues.jboss.org/browse/TEIIDDES-971
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 7.2
Environment: JBDS 4.0
Reporter: Joel Tosi
When mapping data in side Designer, a user is forced to bring in all dependencies (think
tables with foreign key dependencies) in order to have a valid model. You should be able
to override this - make the user aware of the missing data and allow user to accept the
limitation.
Think of a scenario where there is a large database, with say 100 tables. Tons of
foreign keys, etc. If a user wants to create a model against one table that has one
foreign key (and bringing in its dependency brings another foreign key....etc) - if the
user doesn't need the information from the related table for their modeling, then they
should be allowed to override the warning and model without the dependency.
To reproduce - create a relational store and create 10 tables (A - J) - A has a foreign
key to B, B to C, and so on. In designer, be able to override the warning when trying to
model against just A.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: