[
https://issues.apache.org/jira/browse/CLOUDSTACK-9871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969444#comment-15969444
]
ASF GitHub Bot commented on CLOUDSTACK-9871:
--------------------------------------------
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/2037
@pdion891: As far as I know this should have no impact on 5.6
We simply tell the SQL server which modes we want to have enabled. Starting
with MySQL 5.7 various modes have been disabled by default, we just enable them
again.
On the long run we should fix the queries CloudStack executes.
> MySQL 5.7 compatibility
> -----------------------
>
> Key: CLOUDSTACK-9871
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9871
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.10.0.0
> Environment: Ubuntu 16.04, MySQL 5.7
> Reporter: Wido den Hollander
> Priority: Minor
> Labels: jdbc, mysql
>
> MySQL 5.7 comes with a more strict SQL mode by default which causes problems
> for CloudStack as the queries it executes are not all compatible with MySQL
> 5.7.
> https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html
> A work-around is setting the sql_mode to a more relaxed mode in the my.cnf:
> [mysqld]
> sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
> In the future CloudStack should be fully compatible with the new SQL mode.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
