[MDEV-13427] INSERT permission error on 2nd level view during mysql_upgrade Created: 2017-08-02 Updated: 2023-04-27 |
|
| Status: | Confirmed |
| Project: | MariaDB Server |
| Component/s: | Authentication and Privilege System, Scripts & Clients, Views |
| Affects Version/s: | 5.5, 10.0, 10.1, 10.1.23, 10.2, 10.3, 10.4, 10.5 |
| Fix Version/s: | 10.4, 10.5 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Hartmut Holzgraefe | Assignee: | Oleksandr Byelkin |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Description |
|
When having two views with a DEFINER that only has SELECT privileges on the underlying table, and the second view using the first one, on running mysql_upgrade the following permission related error is printed for the 2nd level view:
When also giving the INSERT privilege to the DEFINER no error is raised. Only giving SELECT privileges to the definer should be perfectly ok though, no matter how deep views are nested. How to reproduce:
then run mysql_upgrade -f (-f to force execution even if upgrade has already been run for the current version) Result:
|
| Comments |
| Comment by Hartmut Holzgraefe [ 2017-08-02 ] | ||||||||||||||||||||
|
Priority changed to "Minor" as the error message is annoying/confusing, but the view is still usable after running mysql_upgrade | ||||||||||||||||||||
| Comment by Elena Stepanova [ 2017-08-04 ] | ||||||||||||||||||||
|
The message is produced upon REPAIR NO_WRITE_TO_BINLOG VIEW ... which mysql_upgrade issues during operation.
|