MySQL Bugs: #4504: user admin./schema priv. schema is still present even if del. from catalog

Bug #4504	user admin./schema priv. schema is still present even if del. from catalog
Submitted:	10 Jul 2004 20:16	Modified:	27 Jul 2004 0:43
Reporter:	Dejan Drečnik	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.0.6 beta	OS:	Windows (win xp)
Assigned to:	Bugs System	CPU Architecture:	Any

Description:
Hello team, i have a bug to report :)

When adding a new schema and assigning the priviledges to it. It works but when droping a schema in the catalog the schema under the user admin. / schema previledgies stays in, the only way i could delete it is that i open the "mysql" database and delete the record "test db" from the table "db" (used mysql front)
Then used the option in the file to reconnect to the mysql server

Have a nice day.

BYE

How to repeat:
1. select catalog and create a ne schema (test db (db - database))
2. go to user admim. / schema priviledges under the "schemata" there is only one DB "mysql" - first bug the refresh dosent work
3. click in the "schemata" field with left mouse botton and select refrest schemata list then the "test db" appears
4. select the "test db" and add some priviledges "insert, delete, drop" and click apply changes.
5. now go back to catalog and select the "test db" and use command drop schema
6. now go back to user admim. / schema priviledges as you can see that the schema is still present in the schema priviledges and thet the "test db" has still the priviledges - this is wrong if you drop the "test db" in the catalog then in the schema priviledges this schema must dissaper.

The only way i could delete the "test db" from the schema previlegies was, i used MySql Front open the "mysql db" go to table "db" and manualy delete the record

7. go to file and choose reconnect
8 go to user admim. / schema previlegies under and you will see that the "test db" is gone.

Suggested fix:
Don't hae a suggestion on hof to fix this problem, but i thik that you guys will find a way ;)

forgot to set the severity :(

Tested against 1.0.7 beta.

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Additional info:

Hello,

I do not find that the behavior you've described is a bug. As is described in http://dev.mysql.com/doc/mysql/en/GRANT.html at the very end of the page tables (and it's true also for databases) privileges don't vanish if the table is removed. "In MySQL, privileges can be dropped only with explicit REVOKE statements or by manipulating the MySQL grant tables." Of course we could work around it and implement this functionality in the administrator but I think it would not be the right place.
Anyways thanks for reporting!