cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4776) Don't require quotes for true and false
Date Thu, 25 Oct 2012 13:41:13 GMT


Aleksey Yeschenko commented on CASSANDRA-4776:

Please don't commit it yet - I'll attach a patch for cqlsh as well. Soon.
> Don't require quotes for true and false
> ---------------------------------------
>                 Key: CASSANDRA-4776
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Mac OS X, Fedora 16
>            Reporter: John Sanda
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: cql3
>             Fix For: 1.2.0
>         Attachments: 4776.txt
> The docs at describe using
double quotes for an identifier that is a reserved word. The following works as expected,
> cqlsh:test> select "columnfamily" from system.schema_columnfamilies;
> I have a table with a boolean column. In order to insert a boolean value, I have to enclose
it in single quotes. The table looks like,
> CREATE TABLE bool_test (
>   id int PRIMARY KEY,
>   val boolean
> );
> Here is what happens when I try using double quotes,
> cqlsh:rhq> insert into bool_test (id, val) values (4, "false");
> Bad Request: line 1:43 no viable alternative at input 'false'
> The use of single quotes here seems inconsistent with what is described in the docs,
and makes things a bit confusing. It would be nice if single or double quotes could be used
for identifiers that are reserved words. I also think it is a bit counter-intuitive to require
quotes for true and false which are literal values.

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:

View raw message