You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/12/21 01:53:14 UTC

[jira] [Updated] (CASSANDRA-5081) Support null values in PreparedStatements parameters

     [ https://issues.apache.org/jira/browse/CASSANDRA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-5081:
--------------------------------------

    Fix Version/s: 1.2.1
         Assignee: Sylvain Lebresne
    
> 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.1
>
>
> 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