[
https://issues.apache.org/jira/browse/AMQ-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019373#comment-13019373
]
Andras Szerdahelyi commented on AMQ-1942:
-----------------------------------------
Thanks, i will, and it would indeed make a great addition to the spec..
However, i see this particular problem as being outside the JMS ( specifically,
what subset of SQL92 is used for selectors - if that is defined in there at all
) and STOMP specifications. I haven't had a look yet, but i assume all custom
(non-JMS) message headers from a STOMP message are being saved into a string
type property. Wouldn't it make sense to try and make an educated guess about
the intended type of the STOMP header based on its content? At least as far as
numeric and string types go. ( This functionality could depend on configuration
to isolate a possible performance hit )
in the mean time i'll familiarize myself with the STOMP transport, maybe i can
come up with a patch to better illustrate this ( if it is at all feasible )
regards,
Andras
> Numeric selectors do not work in STOMP
> --------------------------------------
>
> Key: AMQ-1942
> URL: https://issues.apache.org/jira/browse/AMQ-1942
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Reporter: Marc Siegel
> Fix For: NEEDS_REVIEWED
>
> Original Estimate: 20h
> Remaining Estimate: 20h
>
> JMS SQL92 numeric selectors, such as
> - < > <= >=
> - BETWEEN val AND val
> Fail to work via STOMP.
> Possible solutions:
> 1. String Operands to numeric selector operators are converted to Numeric
> types
> - only in STOMP?
> 2. Explicit casting to SQL92 Numeric types becomes supported in selectors,
> ie
> - ( INTEGER(field) <= 5)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
