MySQL 5.7.15 unsupported
Posted: Thu 08 Sep 2016 20:11
I've been using MySQL 5.7.14 for a while. I've experienced some issues with some ways querise are generated - especially around user management, but by generating and amending scripts this was an excellent tool.
On one of my rackspace cloud instances, my service provider has now upgraded to MySQL 5.7.15. While I cannot find the cause in any CVE records or clearly documented in the release logs. So on one side I'm querying with rackspace why this update was released without allowing any testing to be undertaken.
dbForge MySQL Studio does not support this and displays an error message right after starting the connection. Is there a specific reason for this seemingly arbitrary limitation and if not is there a workround? I mean most of the SQL Syntax has not changed and it's massively impacting my ability to compensate other issues of this release that I have to use a database IDE that I'm not as familiar with.
Note I'm using 7.1.13.
On one of my rackspace cloud instances, my service provider has now upgraded to MySQL 5.7.15. While I cannot find the cause in any CVE records or clearly documented in the release logs. So on one side I'm querying with rackspace why this update was released without allowing any testing to be undertaken.
dbForge MySQL Studio does not support this and displays an error message right after starting the connection. Is there a specific reason for this seemingly arbitrary limitation and if not is there a workround? I mean most of the SQL Syntax has not changed and it's massively impacting my ability to compensate other issues of this release that I have to use a database IDE that I'm not as familiar with.
Note I'm using 7.1.13.