Menu
▾
▴
#20 Database timestamp field size too small
CrashFix is using too small a data type for timestamp in (I believe) 3 tables. The problem is hidden in MySQL 5.4 but with MySQL 5.7 analysing a crash report results in: -
There were some processing errors:
CDbCommand failed to execute the SQL statement: SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'timestamp' at row 1. The SQL statement executed was: INSERT INTO `tbl_module` (`crashreport_id`, `name`, `sym_load_status`, `file_version`, `timestamp`, `matching_pdb_guid`) VALUES (:yp0, :yp1, :yp2, :yp3, :yp4, :yp5)
The maximum value for an int is 2147483648. I have many records with a timestamp of 2147483647 which is what MySQL sets it to when the value to be stored is too large.
The incorrect data is in the MySQL 5.4 database but MySQL 5.7 blocks the SQL.
I can change the field type to bigint to solve the problem but what will be the consequences of the wrong timestamp recorded in the tables tbl_bug_change, tbl_module and tbl_operation?
