[civicrm-core.git] / CRM / Upgrade / Incremental / sql / 5.4.alpha1.mysql.tpl

{* file to handle db changes in 5.4.alpha1 during upgrade *}

{*
v4.7.20 updated these colums so that new installs would default to TIMESTAMP instead of DATETIME.
Status-checks and DoctorWhen have been encouraging a transition, but it wasn't mandated, and there
was little urgency... because `expired_date` was ignored, and adhoc TTLs on `created_date` had
generally long windows. Now that we're using `expired_date` in more important ways for 5.4,
we want to ensure that these values are handled precisely and consistently.
*}

ALTER TABLE civicrm_cache
  CHANGE created_date created_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP COMMENT 'When was the cache item created',
  CHANGE expired_date expired_date  TIMESTAMP NULL DEFAULT NULL COMMENT 'When should the cache item expire';
Commit	Line	Data
a57aaa08	1	{* file to handle db changes in 5.4.alpha1 during upgrade *}
6f63cf57 TO	2
	3	{*
	4	v4.7.20 updated these colums so that new installs would default to TIMESTAMP instead of DATETIME.
	5	Status-checks and DoctorWhen have been encouraging a transition, but it wasn't mandated, and there
	6	was little urgency... because `expired_date` was ignored, and adhoc TTLs on `created_date` had
	7	generally long windows. Now that we're using `expired_date` in more important ways for 5.4,
	8	we want to ensure that these values are handled precisely and consistently.
	9	*}
	10
	11	ALTER TABLE civicrm_cache
	12	CHANGE created_date created_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP COMMENT 'When was the cache item created',
	13	CHANGE expired_date expired_date TIMESTAMP NULL DEFAULT NULL COMMENT 'When should the cache item expire';