[
https://jira.jboss.org/jira/browse/TEIID-183?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-183.
----------------------------------
Resolution: Deferred
both the xml connector and proc relational now support in. The only scenario that is not
covered is the use of or - which for multiple parameter values should just be written as
an in.
In general there's a case to be made to support a or b as a and not(b) union all b and
not(a) union all a and b OR for distinct results as a union b. This query expansion
should only be done when both a and b are both separately supported for pushdown and
result in significantly less rows being returned than the query without criteria. Marking
as deferred until a compelling use case comes up for this scenario.
user "or" and "in" criteria should generate
multiple queries in some situations
-------------------------------------------------------------------------------
Key: TEIID-183
URL:
https://jira.jboss.org/jira/browse/TEIID-183
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.x
Reporter: Steven Hawkins
Fix For: 6.3
Defect Tracker #23857: Since web services and relational wrappers around procedures do
not support "in" or "or" criteria, an enhancement would be union the
results of multipe queries rather than not pushing down the criteria or not validating the
query entirely.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira