[teiid-issues] [JBoss JIRA] (TEIID-5177) Enforce stricter naming in SQL/DDL

[Steven Hawkins (JIRA)]

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

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


By default we will accept only unqualified names where the current schema is expected - or a non-schema object is named, such as a role.

There is a flag that has been added for backwards compatibility org.teiid.requireUnqualifiedNames with a corresponding doc update. 

> Enforce stricter naming in SQL/DDL
> ----------------------------------
>
>                 Key: TEIID-5177
>                 URL: https://issues.jboss.org/browse/TEIID-5177
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 10.1
>
>
> Multi-part identifiers in Teiid SQL have lax handling due to an early design decision to allow Teiid queries to mimic any naming/quoting used in a native query.  The side effects of this is that '.' is not allowed in a column nor schema name, that quoting is effectively ignored - for example using a multi-part identifier in a DDL create does not scope to that schema:
> create view "foo"."bar" ...
> creates "foo.bar" in the current schema rather than bar in the foo schema.  
> We should at least introduce flags for strict handling and make sure ddl is compatible as possible.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)