[
https://issues.jboss.org/browse/TEIIDDES-188?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIIDDES-188.
-------------------------------------
Fix Version/s: (was: Future)
Resolution: Rejected
The model was imported to not use fully qualified source names. If the import uses fully
qualified names, then the name in source attribute will include the schema name and work
as expected.
The expectation that we would use a modeled schema entry is another issue. Currently
modeled schemas and catalogs only affect the Teiid runtime name of the table. To be exact
a runtime table name is broken down as:
catalog = vdbname
schema = model name
table name = [modeled catalog.][modeled schema.]table name
Then for the generated JDBC source queries all that matters is the name in source on the
table.
Database Schema not used in sql query
-------------------------------------
Key: TEIIDDES-188
URL:
https://issues.jboss.org/browse/TEIIDDES-188
Project: Teiid Designer
Issue Type: Bug
Components: Data Preview
Affects Versions: 6.0.0
Environment: Ubuntu 9.x
eclipse 3.4.2
teiid_designer_6.0.0.v20090427_SNAPSHOT
Postgresql 8.2
postgresql-8.3-604.jdbc4.jar
Reporter: Ben Truitt
Attachments: core_dev_public.xmi
It looks like the database schema specified in the XMI file for the model is not being
used when generating the SQL query to preview data from the model.
I'm attaching my model XMI file. Note the schema is named "rollback".
However, the SQL query generated does not include the schema name, instead it only
includes the table name.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira