[
https://issues.apache.org/jira/browse/CASSANDRA-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346969#comment-14346969
]
Sam Tunnicliffe commented on CASSANDRA-8850:
--------------------------------------------
bq. And while we are at it, enforce that role names are always quoted strings.
No need to carry that CREATE USER mistake to CREATE ROLE, etc.
The issue with this is that it means things bit messy with some statements
which used to relate to users, but now relate to roles basically
GRANT/REVOKE/LIST PERMISSIONS. For those, we'd need to support both identifiers
& strings to maintain backwards compatibility. What's the motivation for
enforcing role names as strings and is it worth it?
> clean up options syntax for create/alter role
> ----------------------------------------------
>
> Key: CASSANDRA-8850
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8850
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Fix For: 3.0
>
> Attachments: 8850-v2.txt, 8850.txt
>
>
> {{CREATE/ALTER ROLE}} syntax would be improved by using {{WITH}} and {{AND}}
> in a way more consistent with other statements.
> e.g. {{CREATE ROLE foo WITH LOGIN AND SUPERUSER AND PASSWORD 'password'}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
