[
https://issues.jboss.org/browse/TEIID-4333?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-4333:
------------------------------------
My initial testing with changing SupportsComapareCriteriaOrdered = true appears to be
working when performing LT, LTE, GT and GTE on string columns.
I'm using the following query:
select name, id, email from PersonMatCache.Person where email > 'Bx' and email
<= 'Mz'
which is producing query:
OPTIMIZATION COMPLETE:
PROCESSOR PLAN:
AccessNode(0) output=[PersonMatCache.Person.name, PersonMatCache.Person.id,
PersonMatCache.Person.email] SELECT g_0.name, g_0.id, g_0.email FROM PersonMatCache.Person
AS g_0 WHERE (g_0.email > 'Bx') AND (g_0.email <= 'Mz') LIMIT 100
and appears to be returning the correct results. More testing is needed, but this appears
to be good news with the fix in JDG 6.6.
Change default of SupportsComapareCriteriaOrdered to true
---------------------------------------------------------
Key: TEIID-4333
URL:
https://issues.jboss.org/browse/TEIID-4333
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 9.x
Reporter: Van Halbert
Assignee: Van Halbert
Change the default of translator capability SupportsComapareCriteriaOrdered from false to
true. In JDG 6.6, a fix was made to correct the issue with querying LT, LTE, GT and GTE
on string columns.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)