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

virtual function with same name as source function is always ambiguous

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 15.0
    • Component/s: Query Engine
    • Labels:
      None
    • Sprint:
      DV Sprint 65
    • Story Points:
      0.5

      Description

      If we have both a virtual schema and a source schema function with the same name, f1, then issuing a query like:

      select v.f1()...

      will always report that v.f1 is ambiguous because in the resolving of the function the logic at one point disregards the schema.

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 hours
                  3h
                  Remaining:
                  Time Spent - 1 hour, 30 minutes Remaining Estimate - 1 hour, 30 minutes
                  1h 30m
                  Logged:
                  Time Spent - 1 hour, 30 minutes Remaining Estimate - 1 hour, 30 minutes
                  1h 30m