Your "hacky ways" shouldn't include 'renaming files' (that's under the "crazy ways"). The broad and loose connections between authentication, triggers, events, foreign keys, sequences, replication filters, added to the complexity of renaming databases so much it couldn't be made reliable with the available engineering effort.

What's your use case for waning a rename database?

There are many reasons when one would like to rename a database.

Things like when restoring to a Test server, rename it to "mydatabase_Test".

Or, for example, when one is expanding the business, and wants to make their original database more meaningful, like from "main" to "mybusiness1", so that it distinguishes from other newer databases on the server.

Or, when someone is leaving "cPanel", which forced you to have the cPanel username as prefix, and now you want to remove it. E.g. "cpaneluser_MyBusiness" to just "MyBusiness".

These are just small examples. Renaming database should be a basic feature to have, anyway.

I used a Percona script to do the job when I created this ticket. It worked quite well.

https://www.percona.com/blog/2013/12/24/renaming-database-schema-mysql/

I think a script submission that starts by disclosing its known limitations would be acceptable. Unlike the percona script, something that uses `GRANT/REVOKE` to move privs would be appreciated.

Yes, it was removed from MySQL because it had too many very hard to fix bugs