Remove strict sql_mode setting which breaks apps.

Strict sql_mode settings are very application specific, many will simply
not work with them. This setting was likely inherited from some other
production MySQL config file and is not appropriate for a generic
configuration. Specifically, this broke the MySQL package maintainer
scripts.

Change-Id: I068fcc7b3c770541d3d1ecfb372384750f182584
This commit is contained in:
Clint Byrum 2013-04-04 10:54:27 -07:00
parent ef7d0307ff
commit 352516381f

View File

@ -19,7 +19,6 @@ myisam_recover = FORCE,BACKUP
max_allowed_packet = 16M max_allowed_packet = 16M
max_connect_errors = 1000000 max_connect_errors = 1000000
skip_name_resolve skip_name_resolve
sql_mode = STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY
sysdate_is_now = 1 sysdate_is_now = 1
innodb = FORCE innodb = FORCE
innodb_strict_mode = 1 innodb_strict_mode = 1