Modify schema change helper with guard clause
requested to merge 223766-modify-cleanupconcurrentschemachange-with-check-for-columns-existing into master
What does this MR do?
In the rare case that the old_column doesn't exist for the cleanup process, we should guard and skip the execution that assumes it is there.
This was found during copy of the implementation in https://gitlab.com/gitlab-services/version-gitlab-com/-/merge_requests/493/diffs#note_365907790
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides - [-] Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Related to #223766
Edited by Mayra Cabrera