1 個回答
- 最新
- 最多得票
- 最多評論
0
Hello,
Thank you for sharing detailed information for this issue.
Though unfortunately I had attempted to reproduce this issue by following the listed steps and had been unable to do so.
I first created a new Aurora 3.03 cluster (compatible with MySQL 8.0.26). I then connected to the writer instance with the default master user. With the master user I performed the following:
CREATE SCHEMA new_schema;
- 1 row(s) affected
CREATE TABLE new_schema.test_table (id int);
- 0 row(s) affected
CREATE USER `my-user`@`%` IDENTIFIED BY 'password';
- 0 row(s) affected
GRANT ALL PRIVILEGES ON `new\_schema`.* TO `my-user`@`%`;
- 0 row(s) affected
SHOW GRANTS for `my-user`;
- 2 row(s) returned
GRANT USAGE ON *.* TO `my-user`@`%`
GRANT ALL PRIVILEGES ON `new\_schema`.* TO `my-user`@`%`
I then connected to the instance with my-user
and performed the following:
SELECT * FROM new_schema.test_table;
- 0 row(s) returned
As I had not inserted anything to the test_table
no rows were returned but I had not encountered the permission denied error when attempting to select from the table.
相關內容
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前