5.65.alpha1 - Define pre-upgrade snapshots (Option B) #26999
Merged
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.
Overview
For data-structures that are modified by the 5.65.alpha1 upgrade, create some snapshots (just in case we discover some schema problem later on).
This is one of two options. Option B uses a new Smarty helper (
{crmUpgradeSnapshot}
) and puts the calls inline (adjacent to the actual upgrade steps). This should be an easier exemplar to follow in the future. It gives up support for pagination (which shouldn't matter for the relatively small data-sets involved).(For Option A, see #26998.)
Before
After
*.mysql.tpl
file.