-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old data are not detected #33
Comments
hhorak
added a commit
to hhorak/mariadb-container
that referenced
this issue
Apr 25, 2017
Based on the MYSQL_UPGRADE variable and based on the datadir version detected, we either warn user about incompatibilities, or run one of the specified tools: * mysql_upgrade * mysqlcheck --analyze --all-databases * mysqlcheck --optimize --all-databases This should also fix sclorg#33
hhorak
added a commit
to hhorak/mariadb-container
that referenced
this issue
Apr 25, 2017
Based on the MYSQL_UPGRADE variable and based on the datadir version detected, we either warn user about incompatibilities, or run one of the specified tools: * mysql_upgrade * mysqlcheck --analyze --all-databases * mysqlcheck --optimize --all-databases This should also fix sclorg#33
test comment.. |
The upgrade is already implemented for a long time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MySQL and MariaDB use versions that consist of three numbers (e.g. 5.6.23). When two versions are different only in the last part, they are compatible, but when upgrading from e.g. 5.6 to 5.7, we need to consider upgrading as described in https://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previous-series.html. Currently, there is no check whether the data come from a different version (incompatible) so it can happen that users by mistake change the version of the image and they can see errors or even data corruption when not using the standard upgrading scenario described in the documentation.
The text was updated successfully, but these errors were encountered: