[
https://issues.apache.org/jira/browse/CASSANDRA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580793#comment-13580793
]
Sylvain Lebresne commented on CASSANDRA-5081:
---------------------------------------------
I note that the patch attached only support nulls for non primary key parts
(which make sense) and not at all in select statements. The reasoning for the
latter is just that support null in select statements is not really doable
efficiently currently as 2ndary indexexes do not index "null" values (and it
wouldn't be trivial to do).
> Support null values in PreparedStatements parameters
> ----------------------------------------------------
>
> Key: CASSANDRA-5081
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5081
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Michaël Figuière
> Assignee: Sylvain Lebresne
> Fix For: 1.2.2
>
> Attachments: 5081.patch
>
>
> Currently whenever developers want to use PreparedStatements, they need to
> ensure that all their parameters are non null or they need to have several
> PreparedStatements for each possible set of non null columns they want to
> store. This is obviously not a satisfying solution considering that 'null'
> values are a commonplace in applications.
> 'null' values should be allowed as parameters of PreparedStatements in Binary
> Protocol to solve this issue.
> This issue is obviously tightly coupled with CASSANDRA-3783 but they might be
> fixed separately.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
