[
https://issues.apache.org/jira/browse/CASSANDRA-17762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583746#comment-17583746
]
Avi Kivity commented on CASSANDRA-17762:
----------------------------------------
One problem is that X = NULL is valid SQL, it just has a different meaning than
CQL. (it means UNKNOWN or NULL). So the syntax can't be deprecated, just the
interpretation. So I think it makes sense to have a config item indicate which
interpretation to use, so applications can be migrated independently of the
update schedule (and problems with mixed version clusters avoided).
> LWT IF col = NULL is inconsistent with SQL NULL
> -----------------------------------------------
>
> Key: CASSANDRA-17762
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17762
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
> Reporter: Avi Kivity
> Priority: Normal
> Fix For: 4.x
>
>
> In SQL, any comparison with NULL is NULL, which is interpreted as FALSE in a
> condition. To test for NULLness, you use IS NULL or IS NOT NULL.
> But LWT uses IF col = NULL as a NULLness test. This is likely to confuse
> people coming from SQL and hamper attempts to extend the dialect.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
