[
https://issues.redhat.com/browse/TEIID-5976?focusedWorklogId=12451599&...
]
Steven Hawkins logged work on TEIID-5976:
-----------------------------------------
Author: Steven Hawkins
Created on: 29/Jun/20 9:39 AM
Start Date: 29/Jun/20 9:39 AM
Worklog Time Spent: 1 hour, 30 minutes
Work Description: This turned out to be easier than expected.
Issue Time Tracking
-------------------
Remaining Estimate: 1 hour, 30 minutes (was: 3 hours)
Time Spent: 1 hour, 30 minutes
Worklog Id: (was: 12451599)
virtual function with same name as source function is always
ambiguous
----------------------------------------------------------------------
Key: TEIID-5976
URL:
https://issues.redhat.com/browse/TEIID-5976
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 15.0
Original Estimate: 3 hours
Time Spent: 1 hour, 30 minutes
Remaining Estimate: 1 hour, 30 minutes
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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)