[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099115#comment-13099115
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
I think the compound_name() function is a reasonable solution for the insert
side, +1.
On the SELECT side, it's a valiant effort, but these examples just doesn't look
like [C|S]QL anymore. Remember that a simple SQL SELECT grammar is
{noformat}
SELECT * | expression [ [ AS ] output_name ] [, ...]
{noformat}
I think adding non-SQL syntax to that is a bad thing to do if we can avoid it.
(I don't think it matters particularly that ";" is also typically used as a
statement delimiter in SQL shells, including cqlsh -- the choice of delimiter
isn't the main problem.)
> CQL support for compound columns
> --------------------------------
>
> Key: CASSANDRA-2474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
> Project: Cassandra
> Issue Type: Sub-task
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Pavel Yaskevich
> Labels: cql
> Fix For: 1.0
>
> Attachments: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
