[
https://issues.jboss.org/browse/TEIIDDES-2807?page=com.atlassian.jira.plu...
]
Steve Tran updated TEIIDDES-2807:
---------------------------------
Description: It would be nice if changes in meta models would automatically propagate
to dependent layers. For example, I update my datasource XMI so that a column has been
added. In my base layer, the select query was "select * from XYZ". The meta
model is not updated with the new column from the datasource XMI until I trigger JBDS to
rebuild the workspace by adding a random space character in the "select * from
XYZ" statement and pressing save. In cases where the select statement is not select
*, it should do nothing since the user has explicitly defined the select. (was: When
starting jDV/EAP within JBDS, a non-fatal error is thrown every time. It can be ignored,
but it's an annoyance that customers have reported.)
Automatic propagation of meta-model changes
-------------------------------------------
Key: TEIIDDES-2807
URL:
https://issues.jboss.org/browse/TEIIDDES-2807
Project: Teiid Designer
Issue Type: Feature Request
Affects Versions: 9.0.3
Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version
6.4.3,
JBoss Developer Studio 8.1.0GA with Teiid Designer plugin
9.0.3.Final.v20150810-1438-B1157
64-bit Windows 7 environment
Reporter: Steve Tran
Assignee: Barry LaFond
Priority: Minor
It would be nice if changes in meta models would automatically propagate to dependent
layers. For example, I update my datasource XMI so that a column has been added. In my
base layer, the select query was "select * from XYZ". The meta model is not
updated with the new column from the datasource XMI until I trigger JBDS to rebuild the
workspace by adding a random space character in the "select * from XYZ"
statement and pressing save. In cases where the select statement is not select *, it
should do nothing since the user has explicitly defined the select.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)