[
https://issues.apache.org/jira/browse/CASSANDRA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724433#comment-17724433
]
Stefan Miklosovic edited comment on CASSANDRA-15046 at 5/19/23 10:24 PM:
-------------------------------------------------------------------------
After all, I do not think that numbering is necessary. If people want to copy
what they did to some script, they would have numbers at the front which they
would need to get rid of first.
If we can not reference it then numbering is irrelevant. I do not think that
referencing is easy thing to do.
was (Author: smiklosovic):
After all, I do not think that numbering is necessary. If people want to copy
what they did to some script, they would have numbers at the front which they
would need to get rid of first.
I we can not reference it then numbering is irrelevant. I do not think that
referencing is easy thing to do.
> Add a "history" command to cqlsh. Perhaps "show history"?
> ----------------------------------------------------------
>
> Key: CASSANDRA-15046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15046
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
> Reporter: Wes Peters
> Assignee: Brad Schoening
> Priority: Low
> Labels: lhf
> Fix For: 5.x
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> I was trying to capture some create key space and create table commands from
> a running cqlsh, and found there was no equivalent to the '\s' history
> command in Postgres' psql shell. It's a great tool for figuring out what you
> were doing yesterday.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
