Closed adanielvv closed 6 years ago
Running DoctorWhen after merging PR #6
`scheduled_date` timestamp NULL DEFAULT NULL,
`start_date` timestamp NULL DEFAULT NULL,
`end_date` timestamp NULL DEFAULT NULL,
Nicer if it would be this?
`scheduled_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
`start_date` timestamp NULL DEFAULT NULL,
`end_date` timestamp NULL DEFAULT NULL,
Or this?
`scheduled_date` timestamp NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
`scheduled_date` timestamp NULL DEFAULT NULL,
is correct as per civicrm-core xml/schema/Mailing/MailingJob.xml#L32-L39 and CRM/Utils/Check/Component/Timestamps.php#L129
My test this AM with updated version seems to have the problems. (I believe it is the new version based on dates on files changed on 11/13 although the version # has not changed.) Still does not work with CiviMail and errors when running on fields in question.
facing the same issue
@aniesshsethh Could you please indicate: a) the version of CiviCRM you're seeing this with? b) the version of MySQL you're running? c) the most recent commit of the Doctor When version you're running?
@MegaphoneJon Sorry, This was fixed via https://github.com/civicrm/civicrm-core/pull/11361
Thanks for the quick response.
Excerpt from show create table civicrm_mailing_job; before and after running DoctorWhen: Before:
After:
Locations where CiviMail expects NULL instead of 0: https://github.com/civicrm/civicrm-core/compare/master...DanielvV:fix_date_check