-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Users can lock unpermitted tables. #37978
Labels
Comments
ti-chi-bot
added
may-affects-4.0
This bug maybe affects 4.0.x versions.
may-affects-5.0
This bug maybe affects 5.0.x versions.
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.0
may-affects-6.1
may-affects-6.2
may-affects-6.3
labels
Sep 21, 2022
Thanks! I understood the privilege check is not implemented yet. |
12 tasks
crazycs520
added
severity/minor
and removed
severity/major
may-affects-4.0
This bug maybe affects 4.0.x versions.
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-5.0
This bug maybe affects 5.0.x versions.
may-affects-6.0
affects-6.1
may-affects-6.2
labels
Sep 21, 2022
#38037 will close this issue. Thanks for the report. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug Report
(Thanks for developing the interesting database. At first, I'm not familiar with TiDB. So, please let me know if I misunderstood something.)
When I test with TiDB v6.1.1, I found users can lock unpermitted tables.
Though I couldn't find the document of
LOCK TABLES
, the PR said the following.And mysql 5.7 also says so.
The behavior seems not to be expected.
1. Minimal reproduce step
enable-table-lock
is enabled.(1) create tables and users as root user
(2) lock tables as non-permitted user
(3) check the table is locked or not.
2. What did you expect to see? (Required)
I expected the permission error happens like MySQL when executing (2) procedure. The following is MySQL's error message.
3. What did you see instead (Required)
No error occurred and the user can get the lock of the unpermitted table.
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: