Vladimir, Taras,
Please help to understand how to improve existing docs. Do you have any
plans on addressing the documented and discussed limitations in regards the
case sensitivity?
--
Denis
On Fri, Jun 8, 2018 at 9:48 AM, aealexsandrov
wrote:
>
https://issues.apache.org/jira/browse/IGNITE-8756
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Documentation should be updated as for me to describe how it designed in
SQL. I will file the issue.
When you use SQL and require to create the user like TesT then just use
quotes. Without quotes, you will create TEST.
In case if you are going to change the password for TesT user via SQL
Thanks Andrei, adding quotes and realizing that case matters made all of the
difference.
I did read the documentation around this but my impression was that a
connection via JDBC should be case insensitive and that does not appear to
be the case. From the documentation:
/For instance, if test
Hi,
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
I was very happy to see that the new 2.5 version of Ignite supports
authentication and I have tested this successfully with the default ignite
user. However, I haven't had much success beyond that. If I try to change
the password on the default ignite user (ALTER USER ignite WITH PASSWORD
