As a db admin, I would like to control the 'drop table' vs 'drop database' privileges separately.
I would like to make sure that a user can drop the tables/views but not the databases.
In a scenario where the privileges are granted right after a database is created and the tables are not known yet, the user can't be blocked from dropping a database.

GRANT DROP ON somedb.* TO 'jeffrey'@'localhost';
simply grants all drop commands including 'drop database'. I would like to have a version of this command which would allow to manage 'drop database'/'drop table' privileges separately.