Mysql Strict Mode Disabled

[HelioHost]

During the recent MySQL upgrade on all servers a new setting known as STRICT_TRANS_TABLES was enabled by default. The MySQL website described strict mode as

Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. A value can be invalid for several reasons. For example, it might have the wrong data type for the column, or it might be out of range. A value is missing when a new row to be inserted does not contain a value for a non-NULL column that has no explicit DEFAULT clause in its definition. (For a NULL column, NULL is inserted if the value is missing.)

Source: http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sql-mode-strict

 

This was causing a number of issues with multiple user's poorly designed SQL queries. It also seems that a surprisingly large number of well known, legitimate website software also suffer from these types of bugs, and stopped working after the recent updates. In order to improve ease of use for our customers we have returned the strict setting to the previous state prior to the upgrades mentioned on Stevie in news post http://www.helionet.org/index/topic/22293-mysql-5621/ and on Johnny in news post http://www.helionet.org/index/topic/21199-mysql-5621/

 

Please don't hesitate to let us know if you're having any trouble with the new MySQL settings. If you have any suggestions on what we should upgrade next we'd love to hear from you. Thanks for being part of the Heliohost community.