Ubuntu 16.04, MySql 5.7 and OVPMS 1.9
Submitted by mckelvey on Tue, 30/08/2016 - 09:20
Greetings All,
On one of my test servers (just for funzies) I updated from Ubuntu 14.04 to 16.04 using the "do-release-upgrade". I must say that it all went VERY smoothly and OVPMS 1.8.1 is working well on it. I see, however, that MySQL was upgraded by default to 5.7 and during the upgrade, several of the OVPMS database tables were altered by a script. Unfortunately, however, I see in the install notes for 1.9 that nothing above MySQL 5.5 is being supported.
So I guess my question is whether that <5.6 restriction is set in stone (as it may affect later database migrations) or 5.7 is OK as this migration has already been made. Just asking, since to roll back to Mysql 5.5 in Ubuntu 16.04 looks like a major pain.
Thanks,
Sam
Re: Ubuntu 16.04, MySql 5.7 and OVPMS 1.9
There are some issues running with MySQL 5.7, although there is a report that it can be made to work, by changing the MySQL sql_mode configuration option.
More details here.
Re: Ubuntu 16.04, MySql 5.7 and OVPMS 1.9
Tim,
Thanks for the reference. The error message noted seemed to address the selection of records for reports, and sure enough, with further testing, I found that I was getting errors when trying to run some reports in 1.8.
Adding the sql_mode line to mysqld.cnf did not seem to help, although placing it in the [mysqld] section of my.cnf did the trick.
I'm not sure how this will work with 1.9 but will wait to see. Do you foresee any problems down the road in doing this? Since I'm not altering the database by any means, my sense is to go with it if I can. It seems to me that I would be better off trying to go with a stock version of the Ubuntu Server than trying to run it with a non-repository MySQL. Any thoughts on that?
Thanks,
Sam
Re: Ubuntu 16.04, MySql 5.7 and OVPMS 1.9
The main issue with upgrading in this manner is that MySQL doesn't officially support skipping release versions. From Supported Upgrade Paths:
Direct upgrades that skip a release level (for example, upgrading directly from MySQL 5.5 to 5.7) are not recommended or supported.
When we do support 5.6/5.7, it won't be through changing the sql_mode option.