[teiid-issues] [JBoss JIRA] (TEIID-2950) Do not schema-qualify the DDL constraint references if they are within the current schema

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-2950.
-----------------------------------

    Fix Version/s: 8.7.1
                   8.8
       Resolution: Done


The resolving logic already checks against the current schema first, so it's fine to make this change back.  However we do have a potential ambiguity since we allow multi-part names in an unquoted manner, but that is a larger issue than this one.

> Do not schema-qualify the DDL constraint references if they are within the current schema
> -----------------------------------------------------------------------------------------
>
>                 Key: TEIID-2950
>                 URL: https://issues.jboss.org/browse/TEIID-2950
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: AdminApi
>    Affects Versions: 8.7
>            Reporter: Mark Drilling
>            Assignee: Steven Hawkins
>             Fix For: 8.7.1, 8.8
>
>
> The DDL constraint statements now contain the model name in order to qualify the schema.  For example : 
> CONSTRAINT FK_Account_ParentId FOREIGN KEY(ParentId) REFERENCES importVDBSrcModel.Account (Id)
> Request that the schema be dropped if the reference is within the current schema.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)