Bug #54149 | RENAME USER migrates table/procedure level privileges, contrary to documentation | ||
---|---|---|---|
Submitted: | 1 Jun 2010 15:10 | Modified: | 3 Jun 2010 18:46 |
Reporter: | Scott Noyes | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[1 Jun 2010 15:10]
Scott Noyes
[2 Jun 2010 16:29]
MySQL Verification Team
Privilege changes seem to be consistent with the description in http://dev.mysql.com/doc/refman/5.1/en/privilege-changes.html - global privileges remain until the next connection; table privileges change for the next query.
[3 Jun 2010 18:46]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.
[3 Jun 2010 19:14]
Paul DuBois
See also Bug#20319.
[3 Jun 2010 19:15]
Paul DuBois
Updated description: RENAME USER causes the privileges held by the old user to be those held by the new user. However, RENAME USER does not automatically drop or invalidate any database objects that the old user created. This applies to databases, tables, views, stored routines, triggers, and events.