Add a missing migration to google_sheets and google_sheets_refunds #184
+134
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
mitodl/hq#6042
Description (What does it do?)
When working on mitodl/unified-ecommerce#222 I noticed there were some missing migration errors. At some point, the PKs on some of the tables within
google_sheetsandgoogle_sheets_refundsswitched fromAutoFieldtoBigAutoField. This adds migrations to these two apps to take care of that change.How can this be tested?
Automated tests should pass. This is not a logic change -
BigAutoFieldis just a biggerAutoFIeldso this should have no effect anywhere else, other than needing to run migrations after updating.