[
https://issues.apache.org/jira/browse/QPID-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727857#comment-14727857
]
ASF subversion and git services commented on QPID-6717:
-------------------------------------------------------
Commit 1700868 from [~astitcher] in branch 'qpid/trunk'
[ https://svn.apache.org/r1700868 ]
Revert "QPID-6717: fix evaluation of BETWEEN and NOT IN when types are
mismatched"
This reverts commit 85ed093ba4beae54c1622000cb7a38cb30889239.
- This change broke handling of the IN construct.
> selector can match incorrectly due to different type for values
> ---------------------------------------------------------------
>
> Key: QPID-6717
> URL: https://issues.apache.org/jira/browse/QPID-6717
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: qpid-cpp-0.34
> Reporter: Gordon Sim
> Assignee: Andrew Stitcher
> Priority: Minor
> Fix For: qpid-cpp-next
>
>
> E.g. a selector "x BETWEEN 1 AND 10" would match for a value of x="foo",
> because of the way the logic is implemented for the between expression, or a
> selector "x NOT IN ('a', 'b', 'c')" would match where x=1, though it should
> not due to the type mismatch.
> From JMS spec: "Only like type values can be compared. One exception is that
> it is valid to compare exact numeric values and approximate numeric values"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
