Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 1 Mar 2013 13:41:13 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12624809.1356008295059.364395.1362145273973@arcas>
In-Reply-To: <JIRA.12624809.1356008295059@arcas>
References: <JIRA.12624809.1356008295059@arcas>
Subject: [jira] [Commented] (CASSANDRA-5081) Support null values in
 PreparedStatements parameters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-5081?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13590520#comment-13590520 ]=20

Sylvain Lebresne commented on CASSANDRA-5081:
---------------------------------------------

I'd be thankful if someone review this quicklyish :)
               =20
> 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=C3=ABl Figui=C3=A8re
>            Assignee: Sylvain Lebresne
>             Fix For: 1.2.3
>
>         Attachments: 5081.patch
>
>
> Currently whenever developers want to use PreparedStatements, they need t=
o ensure that all their parameters are non null or they need to have severa=
l 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.=20
> 'null' values should be allowed as parameters of PreparedStatements in Bi=
nary Protocol to solve this issue.
> This issue is obviously tightly coupled with CASSANDRA-3783 but they migh=
t be fixed separately.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira