Bug #100788 | Bug in MySQL Role MySQL community 8.0.20. | ||
---|---|---|---|
Submitted: | 9 Sep 2020 17:51 | Modified: | 14 Oct 2020 13:25 |
Reporter: | lokesh singhal | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 8.0.20 | OS: | Windows |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
Tags: | MySQL, role |
[9 Sep 2020 17:51]
lokesh singhal
[14 Sep 2020 13:25]
MySQL Verification Team
Hi, trying with 8.0.21, can't reproduce the problem: mysql [localhost:8021] {root} ((none)) > create role Dev_Roles; Query OK, 0 rows affected (0.00 sec) mysql [localhost:8021] {root} ((none)) > GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, -> REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, -> LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, -> EVENT, TRIGGER ON -> incedo_users.* TO Dev_Roles ; Query OK, 0 rows affected (0.01 sec) mysql [localhost:8021] {root} ((none)) > show grants for Dev_Roles; +-------------------------------------------------------------+ | Grants for Dev_Roles@% | +-------------------------------------------------------------+ | GRANT USAGE ON *.* TO `Dev_Roles`@`%` | | GRANT ALL PRIVILEGES ON `incedo_users`.* TO `Dev_Roles`@`%` | +-------------------------------------------------------------+ 2 rows in set (0.00 sec) mysql [localhost:8021] {root} ((none)) > GRANT ALL PRIVILEGES ON `incedo_users`.* TO `Dev_Roles`@`%`; Query OK, 0 rows affected (0.01 sec) mysql [localhost:8021] {root} ((none)) > show grants for Dev_Roles; +-------------------------------------------------------------+ | Grants for Dev_Roles@% | +-------------------------------------------------------------+ | GRANT USAGE ON *.* TO `Dev_Roles`@`%` | | GRANT ALL PRIVILEGES ON `incedo_users`.* TO `Dev_Roles`@`%` | +-------------------------------------------------------------+ 2 rows in set (0.00 sec) mysql [localhost:8021] {root} ((none)) >
[15 Oct 2020 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".