[
https://issues.jboss.org/browse/TEIIDDES-931?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-931:
---------------------------------------
Not sure I agree yet.
Fully qualified Parts example:
* SUPPLIER_ID : *PartsOracle11.PARTSSUPPLIER.SUPPLIER_PARTS.SUPPLIER_ID*
The VDB, when used as a source, treats each Model Name as a schema, so if I had named my
XMI model, PARTSSUPPLIER, then the fully qualified name would have been:
* SUPPLIER_ID : *PARTSSUPPLIER.PARTSSUPPLIER.SUPPLIER_PARTS.SUPPLIER_ID*
... which reflects 2 schema containers
We added this "fully qualified name" feature so Designer could handle importing
from DB's with multiple schema defined, but we don't really have a good/available
test case
Change the default to qualify name in source
--------------------------------------------
Key: TEIIDDES-931
URL:
https://issues.jboss.org/browse/TEIIDDES-931
Project: Teiid Designer
Issue Type: Quality Risk
Components: Import/Export
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Mark Drilling
Fix For: 8.2
Fully qualified name in source entries are a safe default. Just using table names can
lead to conflicts. Also using just table names prevents the costing logic from working.
It would almost be best if we didn't even offer the ability to use unqualified names.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira