You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Artem Budnikov (JIRA)" <ji...@apache.org> on 2018/07/02 12:30:00 UTC
[jira] [Commented] (IGNITE-8756) SQL: CREATE/ALTER USER
documentation should contain information about case sensitivity of username
[ https://issues.apache.org/jira/browse/IGNITE-8756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529809#comment-16529809 ]
Artem Budnikov commented on IGNITE-8756:
----------------------------------------
[~aealeksandrov],
The page mentions that "To create a _case-sensitive_ username, use the quotation (") SQL identifier."
Please verify if that is what you wanted to achieve by creating this issue.
> SQL: CREATE/ALTER USER documentation should contain information about case sensitivity of username
> --------------------------------------------------------------------------------------------------
>
> Key: IGNITE-8756
> URL: https://issues.apache.org/jira/browse/IGNITE-8756
> Project: Ignite
> Issue Type: Improvement
> Components: documentation, sql
> Affects Versions: 2.5
> Reporter: Andrey Aleksandrov
> Assignee: Artem Budnikov
> Priority: Major
> Labels: doc
> Fix For: 2.7
>
>
> Now documentation contains next:
> https://apacheignite-sql.readme.io/docs/create-user#section-description
> For instance, if {{test}} was set as a username then:
> * You can use {{Test}}, {{TEst}}, {{TEST}} and other combinations from JDBC and ODBC.
> * You have to use {{TEST}} as the username from Ignite's native SQL APIs designed for Java, .NET and other programming languages.
> But next behavior exists:
> When you create the user in quotes ("test") using SQL as next:
> CREATE USER "test" WITH PASSWORD 'test'
> It will be created as it was set (in this case it will be test)
> If you create the user without quotes (test) using SQL as next:
> CREATE USER test WITH PASSWORD 'test'
> then username will be stored in uppercase (TEST).
> The same situation with ALTER USER.
> The documentation should be updated to clear that SQL supports case sensitive data too (using quotas).
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)