[
https://issues.jboss.org/browse/TEIIDDES-2635?page=com.atlassian.jira.plu...
]
Barry LaFond closed TEIIDDES-2635.
----------------------------------
Resolution: Won't Do
Dynamic VDB import/export features were intended to be the temporary fix until Komodo work
progresses with VDB Builder (CLI) and another UI Editor/Navigator.
Adding a companion DDL file for each model will open a can of worms, and a boatload of
work, to keep in sync while editing/saving the models.
Marking as Won't Do and banking on the upcoming releases of Komodo tools.
Provide manageability of DDL based models/vdb's and .xmi models
----------------------------------------------------------------
Key: TEIIDDES-2635
URL:
https://issues.jboss.org/browse/TEIIDDES-2635
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling, Usability
Reporter: Van Halbert
Assignee: Barry LaFond
Copying comments from planning:
Per Ramesh, the suggestion/proposal (we talked about this couple times) is to keep a DDL
version of the Model along with the XMI model in separate tab in the Designer and let
users check in the DDL version into the SVN/GIT using "team" feature in the
Eclipse. Since DDL file will be text based, the merge and diff are facilities provided
through Eclipse tools. We need to use the team import feature to update the XMI model when
reading from SVN/GIT. This will give us closest collaboration platform we are looking for
without waiting for Komodo and I believe it is fairly achievable goal.
Barry:
The initial import/export (generate) features for dynamic vdbs perform the needed
operations. Now that we have both *.vdb and -vdb.xml resources we can think more about how
to assist the user. CSV/GIT in Eclipse is certainly an attractive option. Linking a
-vdb.xml file to a *.vdb and auto-saving both is also an option. And as Van said,
differencing via CSV/GIT would be the direction I'd vote for.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)