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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In databases that already contain applications created before the
application_choicetable was introduced, the repo migrations never copyfirst_choice_university_info_for_apply_id,second_choice_university_info_for_apply_id, orthird_choice_university_info_for_apply_idintoapplication_choice(checked V50 through V55, and current queries read onlyApplication.choices). Dropping these columns here permanently discards those users' stored choices; add anINSERT INTO application_choice ... SELECT ... FROM applicationbackfill for each non-null choice order before the drop.Useful? React with 👍 / 👎.