Handle dupe prices during migration #1767
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.
What are the relevant tickets?
N/A
Description (What does it do?)
Fixes a migration failure caused by old unpublished runs with duplicate prices.
How can this be tested?
On the main branch:
./manage.py migrate learning_resources 0070_learningresource_location./manage.py migrate learning_resources, it will fail due to a duplicate key.Additional Context
ETL pipelines currently ensure that prices for any particular resource and run are unique, but RC and prod have some old unpublished runs still around from before this was implemented, causing a migration error.