Facebook
Twitter
websavers
Regular Pleskian
Magento 2.0 now requires MySQL 5.6 or higher and a bunch of MySQL User capabilities that Plesk currently does not assign to MySQL users.
I know that Plesk simply uses the system installed MySQL server, so upgrades to that are beyond Plesk's purview. As a result of this we set up two dedicated DB servers one with Percona 5.6 and one with Percona 5.7 (high performance MySQL drop in replacement).
We then added each of those servers as Database Server sources in Plesk and created a database and user on there successfully. However installing Magento fails when specifying the newly created database because it's looking for the following MySQL user rights:
REFERENCES, EXECUTE, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER
None of which are granted when creating a user with 'full' permissions using Plesk.
It would be great if we could have Plesk detect the MySQL server version and allow the application of those rights to MySQL users, when the server supports them. This way we can support applications like Magento 2.0 on a Plesk server.
-Jordan
I know that Plesk simply uses the system installed MySQL server, so upgrades to that are beyond Plesk's purview. As a result of this we set up two dedicated DB servers one with Percona 5.6 and one with Percona 5.7 (high performance MySQL drop in replacement).
We then added each of those servers as Database Server sources in Plesk and created a database and user on there successfully. However installing Magento fails when specifying the newly created database because it's looking for the following MySQL user rights:
REFERENCES, EXECUTE, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER
None of which are granted when creating a user with 'full' permissions using Plesk.
It would be great if we could have Plesk detect the MySQL server version and allow the application of those rights to MySQL users, when the server supports them. This way we can support applications like Magento 2.0 on a Plesk server.
-Jordan
