Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Upgrading to MySQL 5.7? Beware the New STRICT Mode

DZone's Guide to

Upgrading to MySQL 5.7? Beware the New STRICT Mode

MySQL 5.7 runs a bit ''stricter'' than older versions. Of course, that can lead to trouble. If that's causing problems, see how to work around it.

· Database Zone
Free Resource

Traditional relational databases weren’t designed for today’s customers. Learn about the world’s first NoSQL Engagement Database purpose-built for the new era of customer experience.

By default, MySQL 5.7 is much “stricter” than older versions of MySQL. That can make your application fail. To temporarily fix this, change the SQL_MODE to NO_ENGINE_SUBSTITUTION (same as in MySQL 5.6):

set global SQL_MODE="NO_ENGINE_SUBSTITUTION";


MySQL 5.7, Dates, and Default Values

The default SQL_MODE in MySQL 5.7 is:

ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION


That makes MySQL operate in “strict” mode for transactional tables.

“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.) Strict mode also affects DDL statements such as CREATE TABLE.” For more, check out the documentation.

That also brings up an interesting problem with the default value for the date/datetime column. Let’s say we have the following table in MySQL 5.7 and want to insert a row into it:

CREATE TABLE `events_t` (
-> `id` int(11) NOT NULL AUTO_INCREMENT,
-> `event_date` datetime NOT NULL,
-> `profile_id` int(11) DEFAULT NULL,
-> PRIMARY KEY (`id`),
-> KEY `event_date` (`event_date`),
-> KEY `profile_id` (`profile_id`)
-> ) ENGINE=InnoDB DEFAULT CHARSET=latin1
-> ;
Query OK, 0 rows affected (0.02 sec)

insert into events_t (profile_id) values (1);
ERROR 1364 (HY000): Field 'event_date' doesn't have a default value


The event_date does not have a default value, and we are inserting a row without a value for event_date. That causes an error in MySQL 5.7. If we can’t use NULL, we will have to create a default value. In strict mod,e we can’t use “0000-00-00” either:

alter table events_t change event_date event_date datetime NOT NULL default '0000-00-00 00:00:00';
ERROR 1067 (42000): Invalid default value for 'event_date'

alter table events_t change event_date event_date datetime NOT NULL default '2000-00-00 00:00:00';
ERROR 1067 (42000): Invalid default value for 'event_date'


We have to use a real date:

alter table events_t change event_date event_date datetime NOT NULL default '2000-01-01 00:00:00';
Query OK, 0 rows affected (0.00 sec)
Records: 0 Duplicates: 0 Warnings: 0

insert into events_t (profile_id) values (1);
Query OK, 1 row affected (0.00 sec)


Or, a most likely much better approach is to change the application logic to:

  • Allow NULLs.
  • Always insert the real dates (i.e. use NOW() function).
  • Change the table field to timestamp and update it automatically if no value has been assigned.

Further Reading

Read the Morgan Tocker’s article on how to transition to MySQL 5.7, and check the full sql_mode documentation.

Learn how the world’s first NoSQL Engagement Database delivers unparalleled performance at any scale for customer experience innovation that never ends.

Topics:
database ,mysql ,strict mode

Published at DZone with permission of Alexander Rubin, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}