[
https://issues.jboss.org/browse/TEIID-3140?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-3140:
------------------------------------
I think there's a bigger discussion to be had here, that the metadata that one can get
by calling an admin function (rather than going thru the jdbc driver) should provide all
the details of the deployed VDB in DDL form. Especially since we appear to be moving
toward the TEIID DDL as the common language in tooling. And in that exported DDL,
ideally, it should look like a dynamic VDB when exported. The simple benefit to this is
it enables VDB's to be transitioned from between tooling and server and will be needed
when Komodo is done.
Add getVDBType() method to the VDB interface
--------------------------------------------
Key: TEIID-3140
URL:
https://issues.jboss.org/browse/TEIID-3140
Project: Teiid
Issue Type: Enhancement
Reporter: Barry LaFond
Assignee: Steven Hawkins
Because Teiid supports mutliple VDB types, any tooling designed to interact (edit,
deploy, undeploy, display etc...) with the runtime VDBs will need to be able to easilly
distinguish what each VDB type is.
Currently Teiid Designer utilizes PREVIEW and defeault VDBs with *vdb* file extensions
and there are 2 types of dynamic VDBs, *xml* and *zip* files backed by DDL model metadata
definitions.
The current VDB interface currently doesn't provide a type.
Request adding something like:
{code}
public enum VDBType {DEFAULT, PREVIEW, XML, DDL}
/**
* @return the vdb type
*/
public VDBType getVDBType();
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)