Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
5.5.41
-
None
-
Linux * 3.10.0-123.20.1.el7.x86_64 #1 SMP Thu Jan 29 18:05:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Description
Deleting a user can break unrelated databases.
The problem, as far as I understand it is that deleting a user, causes all views (and possible other constructs) that he created not to be queryable anymore. Even worse, recreating that user doesn't solve the whole problem, because he has to have enough access rights to actually see the views he created to allow other users to query them.
This seems very arbitrary and unrelated and is highly surprising. I vote to either:
- disable this 'feature' outright (the user who initially created a view / database / table) should not need to stick around (imagine him changing companies, I want to get rid of him!) and the ability of another user to query a construct should not depend on another user being able to see / query it.
- Deprecate it, that is start by adding an option to disable it, and then switch that option to be default on in some future release
Some example error messages that we saw:
SQL Fehler (1449): The user specified as a definer (´$foo´@´%´) does not exist
1356: View '$bar' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them