The scenario is, we have a WordPress boiler plate that we want to clone on every new virtualhost. When we use the clone function in WP Workbench, it automatically names the cloned database with the name of the original (boilerplate) database adding “clone” at the end. Then for the next clone it uses the same database name “boilerplatedb_clone_d2342” etc… imagine over time our mysql will be filled with databases with the same name that can not be traced to the virtual host they are associated with. I would suggest to use the username or something of the new virtual host, and a suffix, or even give the admin a choice at the time of cloning.
Thanks, this is a nice suggestion!
What is a typical setup for a clone in your case? Is it a separate virtual top or sub-server, or just a new directory under the same domain?
As time goes by and future updates go by, look at what you can bring to WP Workbench from phpMyAdmin functions as an example: rename the database and note where this will also have to be changed.
I agree that the name of the database should be chosen by the user/developer and there should be no reference to the app, example: Wordpress, indicate only the minimum and maximum amount of characters. Passwords will be generated based on the update you’ve already shown on GitHub.
It is always a new top, on the root. So the database of the new website could be named related to the new virtual host username, or simply for the admin to type it. Thank you
So, something like newtop_wordpress
would be better?
I think we shouldn’t clutter the “Clone” tab. Instead, it would be better to simply let the user choose the database name, username, and password.

newtop_wordpress
Sounds good to me. I used to do something similar in the past, newtop_wpdb.
Slightly different use case scenario for me as I am making use of the new sub-server option but the premise is the same
In cpanel all databases are in the format
cpaneluseraccount_userinput
Eg
shoulders_wordpress
and I like this.
WP Workbench 1.0.8 will have significantly improved database naming when cloning.
Thank you, awesome

Thank you, awesome
Since you originally reported it, did you get a chance to try the new version 1.0.8 to see if database naming works better now?
I did and it worked, the db name uses the same formula as you install the WordPress as a script, which makes a lot of sense. Thank you