[JBoss JIRA] Created: (TEIIDDES-194) jdbc Oracle import does not create connector
by Luca Gioppo (JIRA)
jdbc Oracle import does not create connector
--------------------------------------------
Key: TEIIDDES-194
URL: https://jira.jboss.org/jira/browse/TEIIDDES-194
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0
Environment: eclipse.buildId=M20080911-1700
java.version=1.6.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT
…
[View More]Command-line arguments: -os win32 -ws win32 -arch x86
Reporter: Luca Gioppo
Importing model from jdbc
Creating a new source for an Oracle 9 DB
using jdbc14.jar and adding to udf (and a second time in the source definition)
the jar from the oracle instant client
the connection work, tables are imported but at hte end of the import the error is:
Error post processing import (extension class=class com.metamatrix.modeler.internal.dqp.ui.jdbc.ConnectorBindingImportPostProcessor)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
14 years, 8 months
[JBoss JIRA] Created: (TEIIDDES-234) WSDL Relational Importer creates tables that could be collapsed out of the model.
by John Doyle (JIRA)
WSDL Relational Importer creates tables that could be collapsed out of the model.
---------------------------------------------------------------------------------
Key: TEIIDDES-234
URL: https://jira.jboss.org/jira/browse/TEIIDDES-234
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0
Reporter: John Doyle
Assignee: John Doyle
Priority: Minor
…
[View More] Fix For: Future
The attached WSDL and XSD's create a model with a Request Table, Response Table, an intermediate table that has only mmid's, and finally a table (Order) containing all of the data. (it is invalid because of JBEDSP-514, but that's not material). While this model valid and will work once the table name conflict from 514 is addressed, it's not optimal. The intermediate table is not required in the model because there is no multiplicity above the Order table. The intermediate table can be removed and the Order table linked directly to the response and the simplicity of the model will be improved with no loss of capability. The importer could be enhanced to recognize this possibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
14 years, 8 months