[
https://issues.jboss.org/browse/TEIIDDES-1212?page=com.atlassian.jira.plu...
]
Dan Florian resolved TEIIDDES-1212.
-----------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Release Notes Text: For JDBC imports, fully-qualified "name in
source" is now working.
Resolution: Done
Problem was the createValidName method was returning a non-null value when the name was
not being changed. Fixed.
Fully Qualified Names in Source doesn't work on JDBC Import
-----------------------------------------------------------
Key: TEIIDDES-1212
URL:
https://issues.jboss.org/browse/TEIIDDES-1212
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.4.2
Reporter: Debbie Steigner
Assignee: Dan Florian
Priority: Critical
Fix For: 7.4.2
Marking the Fully Qualified Source Names on a JDBC Import into Teiid Designer does not
create the correct "Name in Source" property on the tables. It makes them the
tablename only not schema.tablename.
This functionality did work in 7.1.1 but no longer works in 7.4.x, this is a major issue,
most customers do not have the user who is the owner of the schema they are importing, so
they must use fully qualified names to source. If the import doesn't properly add the
name in source then the customer has to manually make this change for every table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira