Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-5177

Enforce stricter naming in SQL/DDL

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 10.1
    • Component/s: Query Engine
    • Labels:
      None

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                shawkins Steven Hawkins
                Reporter:
                shawkins Steven Hawkins
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: