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

The notion of resolving order may need to be extended beyond a schema

    Details

    • Type: Quality Risk
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 9.3, 9.2.1
    • Component/s: Query Engine
    • Labels:
      None

      Description

      With TEIID-4629 it is possible to interleave the definition of schema elements, which is not accounted for by the loading order - and will fail upon later validation/resolving.

      create virtual schema first;
      create virtual schema second;
      set schema second;
      create view x ...;
      set schema first;
      create view y as select * from x;

      the last statement will fail later as we'll try to resolve the schemas in order.

      A similar issue exists with create domain - TEIID-3624

        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: