[
https://issues.jboss.org/browse/TEIID-4813?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4813:
-------------------------------------
If you extended the ODataTranslator what you do with the extra predicate is up to you in
your code, as long as you are returning the right results then everything else should work
fine.
Also, please open any forum discussion before opening a JIRA, as we would like to use JIRA
only for bugs and features, and it will be better for searching. thanks.
Basic support for joins in OData v2
-----------------------------------
Key: TEIID-4813
URL:
https://issues.jboss.org/browse/TEIID-4813
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Damien B
Assignee: Steven Hawkins
It's half a bug, half a feature request :-)
We deal with a perticular OData almost v2 server that uses system functions disguised as
entitities. Basically, "/A('b')/C" works but not "/C?$filter=foo eq
'b'". In order to have that, we've enabled the joins support on the
ODataTranslator, but we still haven't the right query generated. We've traced back
the origin to the optimizer:
* SELECT * FROM a join b ON a.x=b.y WHERE a.x='v'
* is optimized as SELECT <columns> FROM a join b ON a.x=b.y WHERE a.x='v'
AND b.y='v'
The extra induced condition "b.y = 'v'" messes up with the URL
construction. Any idea about how to proceed from there?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)