Facebook
TwitterHello,
It would be nice if during the installation of a product from the Application Vault that you can specify an already existing mysql database (local or on a remote server) to do the install to instead of creating a new one every time. This would also allow sharing of databases as you could set a prefix during the application install via browser (assuming the app supports it of course).
Would also be nice if server side could have a setting to disable installs and only allow file copies.
This would be handy for those hosts that only run remote or centralized databases and do not use any hosted on plesk servers.
It would also be nice if mysql could do a host account prefix and seperator.
For example, if clientA created a database named DB1 it would really be named clientA_DB1 ([prefix][seperator][dbname]) instead of just DB1. This could be enabled/disabled as a server setting, as well as prefix being set globally going forward.
It would be nice if during the installation of a product from the Application Vault that you can specify an already existing mysql database (local or on a remote server) to do the install to instead of creating a new one every time. This would also allow sharing of databases as you could set a prefix during the application install via browser (assuming the app supports it of course).
Would also be nice if server side could have a setting to disable installs and only allow file copies.
This would be handy for those hosts that only run remote or centralized databases and do not use any hosted on plesk servers.
It would also be nice if mysql could do a host account prefix and seperator.
For example, if clientA created a database named DB1 it would really be named clientA_DB1 ([prefix][seperator][dbname]) instead of just DB1. This could be enabled/disabled as a server setting, as well as prefix being set globally going forward.
