]
Steven Hawkins resolved TEIID-5988.
-----------------------------------
Fix Version/s: 15.0
Resolution: Done
Changed the soql generation strategy to only qualify when a specific parent name is set.
Otherwise we are relying upon the context of the table in the immediate from clause. From
what I can see since no correlation is supported this should work - and does for the join
scenarios we have captured in our tests. This change also addresses the dubious query
generation for the testSelfJoinOuterParentToChild case - it now has no qualification on
the inner id column.
[~i3draven] if these changes work for you and there is a specific currently supported
other branch, 13.x or 14.x you would like to see them on let us know.
We have strange behavior with aliases
-------------------------------------
Key: TEIID-5988
URL:
https://issues.redhat.com/browse/TEIID-5988
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Reporter: Renat Eskenin
Assignee: Steven Hawkins
Priority: Major
Fix For: 15.0
Attachments: Снимок экрана от 2020-06-26 12-37-40.png, Снимок экрана от
2020-06-26 12-38-04.png
Original Estimate: 5 hours
Remaining Estimate: 5 hours
We have two SOQL
SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE
Language = 'it' LIMIT 5
SELECT a.ArticleNumber,a.Id,a.KnowledgeArticleId,a.Language FROM Regular_Articles__kav a
WHERE a.Language = 'it' LIMIT 5
This SOQL requests get different responses from SF because in second request we have
alias for table.
It is mystics from SF (we made bug in sf)
How we can call
SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE
Language = 'it' LIMIT 5
in Teiid without aliases?