[
https://issues.jboss.org/browse/TEIID-4719?page=com.atlassian.jira.plugin...
]
Steven Hawkins edited comment on TEIID-4719 at 1/24/17 7:14 PM:
----------------------------------------------------------------
To keep things similar to today that would be the easiest as the ddl, or whatever is
scoped only to the given schema.
So it could be generic as:
{code}
IMPORT SCHEMA {name} FROM {repo} {arg}
{code}
We just need to be clear on the semantics of import - that is the schema can already exist
and we're adding to it.
was (Author: shawkins):
To keep things similar to today that would be the easiest as the ddl, or whatever is
scoped only to the given schema.
So it could be generic as:
IMPORT SCHEMA {name} FROM {repo} {arg}
We just need to be clear on the semantics of import - that is the schema can already exist
and we're adding to it.
Add a ddl equivalent to the metadata tag
----------------------------------------
Key: TEIID-4719
URL:
https://issues.jboss.org/browse/TEIID-4719
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Generally we'll need something that is equivalent to the metadata tag - that can
specify a repo and options. In a zip deployment this will allow splitting the ddl over
multiple files.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)