CRM-21508 Fix column Information for civicrm_mailing.created_date pas… #11361
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…sed to Docker When
Overview
When there was locking mechanisms attached to the civicrm_mailing table to prevent duplicate windows editing mailings. the created_date column was changed to default to NULL to satisfy older MySQL versions. This was not properly updated in the Docker When information array.
Before
Docker When Fails to convert tables
After
Tables convert correctly
Technical Details
As part of 4.7.27 We converted the created_date column to be DEFAULT NULL so we could have a modified_date column which was ON UPDATE CURRENT_TIMESTAMP see https://github.com/civicrm/civicrm-core/blob/master/CRM/Upgrade/Incremental/php/FourSeven.php#L449 and https://github.com/civicrm/civicrm-core/blob/master/CRM/Upgrade/Incremental/php/FourSeven.php#L1382 However in the Timestamps.php array the default of CURRENT_TIMESTAMP was still set which caused this issue civicrm/org.civicrm.doctorwhen#10
Comments
ping @totten @eileenmcnaughton @MegaphoneJon I believe this is the solution to the problem, I have put it against the RC as it was a bug in 4.7.27