[
https://issues.jboss.org/browse/TEIIDDES-1175?page=com.atlassian.jira.plu...
]
Mark Drilling resolved TEIIDDES-1175.
-------------------------------------
Resolution: Done
Resolve issue with model import settings begin set incorrectly. JdbcImporter now keeps
track of the updateModel settings so that it can be swapped out if user later changes
their selection.
Importing a new model when an existing model is selected in the
modeler tree works, but leaves old model info in Data Source props
----------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1175
URL:
https://issues.jboss.org/browse/TEIIDDES-1175
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.6
Environment: Fedora 16
Reporter: Paul Nittel
Assignee: Mark Drilling
Fix For: 7.7
Attachments: ShouldBeOracleSourceInfo.png
I imported from a DB2 source. With that model selected, I right-clicked elsewhere in the
Model Explorer tree and imported a different model. At the last page of the import wizard,
the previously-selected model was the targeted name for this new model. I unchecked update
and changed the name of the model to reflect what was being imported.
After the import had completed, the Data Source item for the imported model had the
information from the old model which had been selected in the tree.
See attached screenshot.
The Connection Profile/Data Source info is correct in new model but the old JdbcSource
object contains the same JdbcSource info as the original/selected model. Need to detect
the change in CP and do a corresponding change to JdbcSource info.
--
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