Skip to content

MySQL sql_mode change #239

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.

Sign up for GitHub

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

Merged
yadvr merged 2 commits into from
Sep 3, 2021
Merged

MySQL sql_mode change #239

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4ff2271
MySQL sql_mode change
harikrishna-patnala Sep 3, 2021
3bad33d
Fixed formatting
harikrishna-patnala Sep 3, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions source/upgrading/upgrade/upgrade_notes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,3 +101,23 @@ added in CloudStack's db.properties file:
db.cloud.driver=jdbc:mysql

db.usage.driver=jdbc:mysql


MySQL 8.0 sql mode change
-------------------------

MySQL mode (sql_mode) has changed in CloudStack db.properties to
"STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,
ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION".

This gets automatically applies to the MySQL session used by CloudStack management server.

If the admin uses MySQL directly and wants to query tables it is advised to change the sql_mode in the corresponding session or globally.

Eg. mysql> set global sql_mode="STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,
"> ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION";
Query OK, 0 rows affected (0.00 sec)

mysql> set sql_mode="STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,
"> ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION";
Query OK, 0 rows affected (0.00 sec)