Invalid default value for 'occurred'

halftrainedharry · March 4, 2025, 2:24pm

As far as I can tell there was a change in MODX 2.8.7 that adds a default value of CURRENT_TIMESTAMP to the “occurred” column.

github.com/modxcms/revolution

Fix default value for modManagerLog.occurred column

modxcms:2.x ← opengeek:pr-16526-2.x

opened 11:53PM - 16 Feb 24 UTC

opengeek

+17 -4

### What does it do? Adds a default value for the datetime column in the modx_m…anager_log table that is compatible with strict modes, which may be enabled in some environments. Re-up of #15736 with migration ### Why is it needed? Beginning with MySQL > 5.7.8 added strict modes ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, NO_ZERO_IN_DATE. With these strict modes enabled, a datetime default value cannot be NULL and must be > '0000-00-00'. ### How to test Install/update on MySQL 5.7.8 ### Related issue(s)/PR(s) Re-up of #15736 Backport of #16526

It used to be that such a default value was only possible for a column of type “TIMESTAMP” and it seems that for MariaDB version 5 this is still the case. I believe it was changed in version 10.