[
https://issues.apache.org/jira/browse/CASSANDRA-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063578#comment-14063578
]
Jonathan Ellis edited comment on CASSANDRA-6910 at 7/16/14 2:58 PM:
--------------------------------------------------------------------
Can you review, [~snazy]?
was (Author: jbellis):
Can you review, [[email protected]]?
> Better table structure display in cqlsh
> ---------------------------------------
>
> Key: CASSANDRA-6910
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6910
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Tupshin Harper
> Assignee: Mihai Suteu
> Priority: Minor
> Labels: lhf
> Attachments: cassandra6910.patch, screenshot-mihai.jpg
>
>
> It should be possible to make it more immediately obvious what the structure
> of your CQL table is from cqlsh. Two minor enhancements could go a long way:
> 1) If there are no results display the column headers anyway. Right now, if
> you are trying to do a query and get no results, it's common to need to
> display the table schema to figure out what you did wrong. Having the columns
> displayed whenever you do a query wouldn't get in the way, and would provide
> a more visual way than by describing the table.
> 2) Along with the first one, if we could highlight the partition/clustering
> columns in different colors, it would be much more intuitively
> understandable what the underlying partition structure is.
> tl;dr: the forms below should each have distinct visual representation when
> displaying the column headers, and the column headers should always be shown.
> CREATE TABLE usertest (
> userid text,
> email text,
> name text,
> PRIMARY KEY (userid)
> )
> CREATE TABLE usertest2 (
> userid text,
> email text,
> name text,
> PRIMARY KEY (userid, email)
> )
> CREATE TABLE usertest3 (
> userid text,
> email text,
> name text,
> PRIMARY KEY ((userid, email))
> )
--
This message was sent by Atlassian JIRA
(v6.2#6252)
