[teiid-issues] [JBoss JIRA] (TEIID-4807) DDL format of a vdb lacks import information

Steven Hawkins (JIRA) issues at jboss.org
Fri Mar 10 14:46:00 EST 2017


     [ https://issues.jboss.org/browse/TEIID-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-4807.
-----------------------------------
    Resolution: Done


Rolled back the full DDL export for now as we need to be clear what the intent of that export is.

Since there is a specific conversion utility (which also had the .vdb logic rolled back) that lessens the need to introduce logic into the admin.  Also as mentioned in TEIID-4765, we are not properly ensuring statement order from imported sources such that the ddl is generally valid when interpreted as statements.

That's not to say that we won't need functionality like this later.

> DDL format of a vdb lacks import information
> --------------------------------------------
>
>                 Key: TEIID-4807
>                 URL: https://issues.jboss.org/browse/TEIID-4807
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 9.3, 9.2.1
>
>
> Database and schema imports are not represented from the admin getSchema logic.  It looks better that we still restrict this to just a schema for now.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the teiid-issues mailing list