[TRAFODION-2791] 'Not casespecific' column comparison returns wrong
'Not casespecific' column comparison returns wrongresult, now like and t.c1=t.c2 not support
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
jenkins, ok to test
Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/2193/
Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/2193/
-1 You may need to study RangeSpecs a bit more before solving this problem.
Hi again, here is a suggestion: Change method OptRangeSpec::buildRange() and add a check whether a comparison operation (ITM_EQUAL, ITM_LESS, etc.) involves a case-inspecific comparison. If so, then set the local variable isRange to FALSE. This should avoid getting into this problem, as there will be no more RangeSpecs for case-inspecific comparisons.
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/2289/
Can one of the admins verify this patch?
Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/2289/
core/TEST032 and core/TEST038 are failing with compiler assertion errors. Those need to be fixed before we can merge this change.
Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/2890/
Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/2890/
Can one of the admins verify this patch?
Can one of the admins verify this patch?