|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I'm not sure I follow you completely. Are you talking more about the concept of adding models/schema? As per some of the thoughts around
TEIID-2057and the open shift vdb builder, you could easily have admin/ddl methods for that as well.Speaking generally the vdb.xml concept is for convenient deployment and so that we don't have to express some of higher-level or idiosyncratic concepts in ddl against an operational server. It of course is entirely unnecessary, but that doesn't really matter for what we're talking about here - you could just as easily allow an updatable metadata repository to contribute model definitions.