You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2013/04/10 20:08:16 UTC

[jira] [Updated] (CASSANDRA-5452) Allow empty blob literals in CQL3

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

Sylvain Lebresne updated CASSANDRA-5452:
----------------------------------------

    Attachment: 5452.txt

Trivial patch attached.
                
> Allow empty blob literals in CQL3
> ---------------------------------
>
>                 Key: CASSANDRA-5452
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5452
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.5
>
>         Attachments: 5452.txt
>
>
> The current grammar don't allow empty blob literals (so '0x'). The goal here is to allow the following syntax for that:
> {noformat}
> INSERT INTO test(k, b) VALUES (0, 0x)
> {noformat}
> I'll admit that '0x' is not the most beautiful syntax ever, but I think that's the only thing that make sense.
> I'll note that currently there is 2 workaround to insert empty blobs: you can either use prepared statement (not a bad idea when using blobs anyway) or, because we've deprecated but still support until 2.0 using strings as blob (to allow upgrade from 1.2.0 to 1.2.1), you can use an empty string. I'll note that this latter workaround will trigger a deprecation warning in the log however and will stop working in 2.0.

--
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