[ 
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186339#comment-13186339
 ] 

paul cannon commented on CASSANDRA-2474:
----------------------------------------

bq. I do have my own minor gripe about this, actually, which is that single 
quotes means "string literal" to SQL. We should stick to double quotes when we 
need identifier disambiguation.

Except in SQL, integers, floats, uuids, etc., aren't valid column names. CQL 
already supports using (quoted) string literals as column names, which seems 
like it would be useful for disambiguating text column names that might 
otherwise parse as integers or whatever. It seems more natural to keep the 
string-literal notation used everywhere else in the language intact for column 
names.

Maybe this is no longer important with the new semantics, though. Haven't 
thought it through yet.
                
> CQL support for compound columns and wide rows
> ----------------------------------------------
>
>                 Key: CASSANDRA-2474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>              Labels: cql
>             Fix For: 1.1
>
>         Attachments: 0001-Add-support-for-wide-and-composite-CFs.patch, 
> 0002-thrift-generated-code.patch, 2474-transposed-1.PNG, 
> 2474-transposed-raw.PNG, 2474-transposed-select-no-sparse.PNG, 
> 2474-transposed-select.PNG, cql_tests.py, raw_composite.txt, 
> screenshot-1.jpg, screenshot-2.jpg
>
>
> For the most part, this boils down to supporting the specification of 
> compound column names (the CQL syntax is colon-delimted terms), and then 
> teaching the decoders (drivers) to create structures from the results.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to