[
https://issues.apache.org/jira/browse/CASSANDRA-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997922#comment-13997922
]
Robert Stupp commented on CASSANDRA-7225:
-----------------------------------------
It's about the sentence from {{help select_where}} in cqlsh:
{code}
cqlsh:demo> help select_where
SELECT: Filtering rows
SELECT ... WHERE <key> = keyname AND name1 = value1
SELECT ... WHERE <key> >= startkey and <key> =< endkey AND name1 =
value1
SELECT ... WHERE <key> IN ('<key>', '<key>', '<key>', ...)
...
Note: The greater-than and less-than operators (> and <) result in key
ranges that are inclusive of the terms. There is no supported notion of
"strictly" greater-than or less-than; these operators are merely
supported as aliases to >= and <=.
{code}
> < is <= and > is >= in CQL
> --------------------------
>
> Key: CASSANDRA-7225
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7225
> Project: Cassandra
> Issue Type: Bug
> Reporter: Robert Stupp
>
> Just a small line of text in cqlsh "help" command indicates that < is <= and
> > is >= in CQL.
> This is confusing to many people (including me :) ) because I did not expect
> < to return the "equals" portion.
> Please allow distinct behaviours for <, <=, > and >= in CQL queries. Maybe in
> combination with CASSANDRA-5184 and/or CASSANDRA-4914
--
This message was sent by Atlassian JIRA
(v6.2#6252)
