I found out the cause of this issue. If you’re running MySQL Server version 5.7.8 or above, the default behavior in SQL_MODE was changed and interrupts the query in question:
CREATE TABLE razuna.raz1_upc_template ( upc_temp_id varchar(100), upc_date_create timestamp, upc_date_update timestamp, upc_who varchar(100), upc_active varchar(1) DEFAULT '0', host_id int, upc_name varchar(200), upc_description varchar(2000), PRIMARY KEY (upc_temp_id), key raz1_upc_t_upc_active (upc_active), key raz1_upc_t_host_id (host_id) ) ENGINE=InnoDB CHARACTER SET utf8 COLLATE utf8_general_ci ROW_FORMAT=DYNAMIC
If you look at the server variable SQL_MODE, you’ll see:
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
The two modes NO_ZERO_IN_DATE and NO_ZERO_DATE are stopping the query and giving us the error (Error #1067, according to my SQL client).
To compensate for Razuna’s SQL, I added the following line to my mysqld.cnf file (or alternatively, the [mysqld] section in my.cnf, depending on which distribution you’re using):
sql-mode="ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
The installation/upgrade went smooth after that.
References:
https://stackoverflow.com/questions/36882149/error-1067-42000-invalid-default-value-for-created-at