MySQL Bugs: #40945: Separation of DROP TABLE/DATABASE grant permissions

Bug #40945	Separation of DROP TABLE/DATABASE grant permissions
Submitted:	21 Nov 2008 21:56	Modified:	26 Nov 2008 5:16
Reporter:	Kate Salholm	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Security: Privileges	Severity:	S4 (Feature request)
Version:	5.0.41	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	database, Drop, grant, permissions, table

Description:
As a part-DBA/part-developer I was troubled when I accidentally dropped one of my databases this morning and in an effort to avoid this happening in future, tried to change my grant permissions. I need to be able to DROP TABLES but don't ever want to be able to DROP DATABASE, I think it would be a real advantage to MySQL to separate this privilege. If I do need to DROP the database I can use my admin account to do this. Please consider!

How to repeat:
Drop a database you didn't mean to, wait a couple of hours for the backup to be reinstated, take multiple calls explaining why there is no data to process.

Suggested fix:
Separate grant permissions for DROP TABLE and DROP DATABASE.

Thank you for a feature request. Isn't it a duplicate of bug #18938?

True enough, however, that feature request was sent in 2006. I thought that as it was originally posted 2+ years ago it might be worth bring it back to your attention?

Duplicate of bug #18938.