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

[21 Nov 2008 21:56] Kate Salholm 
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.
[22 Nov 2008 8:06] Valeriy Kravchuk 
Thank you for a feature request. Isn't it a duplicate of bug #18938?
[25 Nov 2008 22:09] Kate Salholm 
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?
[26 Nov 2008 5:16] Valeriy Kravchuk 
Duplicate of bug #18938.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.