[
https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin...
]
Jan Stastny commented on TEIID-4976:
------------------------------------
[~jolee] Do you have more detailed information about this issue?
I mean, the resulting dependent source query depends on the current contents in the first
source. Can we count on the fact, that customer's data are in the correct state, where
this fix helps to resolve the issue?
I'd be hesitant to state, that we fixed the issue, but after customer's database
changes, the issue reappears. I understand, that there is not loss of data, or incorrect
data being returned, but that hadn't been the case in the first place, right?
criteria duplicated when criteria includes the same columns as
dependent join criteria
--------------------------------------------------------------------------------------
Key: TEIID-4976
URL:
https://issues.jboss.org/browse/TEIID-4976
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.7.11.6_2
Reporter: Marc Shirley
Assignee: Steven Hawkins
Fix For: 10.0, 8.12.x-6.4, 8.12.12.6_3, 8.7.13.6_2
Submitting a query that uses the same column for the join condition and criteria results
in the criteria being duplicated on the dependent side of the join.
For example:
SELECT * FROM A, B
WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B;
Results in the dependent side query looking like:
SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN
('1','2','3');
This looks to have already been resolved in later versions, but I was not able to find
the original JIRA that would have addressed this issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)