Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Duplicate
-
Affects Version/s: 4.3.0
-
Fix Version/s: 4.3.0
-
Component/s: None
-
Labels:None
Description
Pradeep found in working on CRM-11260 that when testing upgrade from 3.1 to 4.2.6
No FK created in fresh install of 4.2.6 for autorenewal_msg_id in civicrm_membership_type, but in upgrade FK constraint was created (v3.3.2).
Depending on if the constraint is or is not a good idea, seems like a 4.3 upgrade should either drop the FK Constraint or one should be included the tarball and in 4.3 upgrade if it doesn't exist.