[
https://issues.jboss.org/browse/TEIID-4784?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-4784.
-----------------------------------
Resolution: Done
Labels: (was: Beta3)
The fix here was quite broad due to intervening changes in the metadata system. We cannot
access the full metadata when initially building the vdb, so all of the logic embedded in
the parser that did this (mostly in alters) needed pulled out to the DatabaseStore.
From there I've also made the alters consistent in not needed to
only act on the current schema - that is you can use qualified names - although we will
still allow you to resolve unqualifed even with the schema set, which can be confusing so
I'll log an issue for that and potentially giving preference to resolving against the
current schema.
I believe the only thing that we require to be in the context of the current schema are
creates - so a follow on issue will be to allow drops to work as qualified as well.
Provide functionality to perform RENAME table in DDL scripts
------------------------------------------------------------
Key: TEIID-4784
URL:
https://issues.jboss.org/browse/TEIID-4784
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 9.3
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Fix For: 10.3, 10.1.4, 10.2.2
Allow rename commands like:
ALTER TABLE "teiidtest" RENAME TO "tmptbl_teiidtest";
This should rename the table name teiidtest in the current schema to tmptbl_teiidtest.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)