[
https://issues.apache.org/jira/browse/IGNITE-8756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529831#comment-16529831
]
Andrey Aleksandrov commented on IGNITE-8756:
--------------------------------------------
[~Artem Budnikov] Thank you but I think that next part of the documentation
isn't fully correct:
-If it's planned to access Ignite from Java, .Net or other programming
languages APIs then the username has to be passed in the *upper-case letters*
from those interfaces.
-You have to use TEST as the username from Ignite's native *SQL APIs designed
for Java*, .NET and other programming languages.
As for me, it meant that in SQL APIs designed for Java you can use only upper
case. But you can also *create* (CREATE USER) and *use* (ALTER USER) values in
camel case like in JDBC/ODBC using quotations.
So I think that "When Case-Sensitive Names are Preferred?" should be updated.
> 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)