[
https://issues.apache.org/jira/browse/CASSANDRA-17762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569185#comment-17569185
]
Benedict Elliott Smith commented on CASSANDRA-17762:
----------------------------------------------------
It's still a change of semantic, and an inconsistency in our behaviour, even if
it only affects the new transaction syntax. I don't think it needs a lengthy
discussion, just a summary of what we have agreed so far (if we have indeed
agreed anything yet) and an invitation for comment or to join the discussion
here.
> 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: [email protected]
For additional commands, e-mail: [email protected]
