[
https://issues.jboss.org/browse/TEIIDDES-2463?page=com.atlassian.jira.plu...
]
Van Halbert updated TEIIDDES-2463:
----------------------------------
Description:
Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on
top of the source model (1-for-1) so that as changes are made to the data source, they
don't impact the out-side-layer (Data Access Layer) the client apps use. Which is
part of the reason why layering of models works.
So the enhancement is to add the ability to refresh a view model from the source model.
Example. 1st time layer1 is created (transformed) from source, all views are included.
And down the road, the data source adds new tables (or in layer1 model, views had been
removed). Now you want to refresh the layer1 model. Add an option to add in
(transform) any missing tables, as was done when the layer1 model was originally created.
So that the user doesn't have to manually figure out what's new and add them
one-at-a-time.
was:
Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on
top of the source model (1-for-1) so that as changes are made to the data source, they
don't impact the out-side-layer (Data Access Layer) the client apps use. Which is
part of the reason why layering of models works.
Then enhancement is add the ability to refresh a view model from the source model.
Example. 1st time layer1 is created (transformed) from source, all views are included.
And down the road, the data source adds new tables (or in layer1 model, views had been
removed). Now you want to refresh the layer1 model. Add an option to add in
(transform) any missing tables, as was done when the layer1 model was originally created.
So that the user doesn't have to manually figure out what's new and add them
one-at-a-time.
Add feature to refresh virtual model from source model
------------------------------------------------------
Key: TEIIDDES-2463
URL:
https://issues.jboss.org/browse/TEIIDDES-2463
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 9.0
Reporter: Van Halbert
Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on
top of the source model (1-for-1) so that as changes are made to the data source, they
don't impact the out-side-layer (Data Access Layer) the client apps use. Which is
part of the reason why layering of models works.
So the enhancement is to add the ability to refresh a view model from the source model.
Example. 1st time layer1 is created (transformed) from source, all views are included.
And down the road, the data source adds new tables (or in layer1 model, views had been
removed). Now you want to refresh the layer1 model. Add an option to add in
(transform) any missing tables, as was done when the layer1 model was originally created.
So that the user doesn't have to manually figure out what's new and add them
one-at-a-time.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)