-
-
Notifications
You must be signed in to change notification settings - Fork 730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update adjustments #7121
Update adjustments #7121
Conversation
1af5e61
to
687c8ef
Compare
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.
neat 👌
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.
That should do the trick.
💣 Deployment failed:
We must not repeat the table name. |
687c8ef
to
fea6ca5
Compare
Updated 👍 I gave it a quick try locally, and the migration ran successfully. |
I deployed to UK staging. Deploy was successful and afterwards there were not outdated adjustments:
|
I also tested the UK production database locally.
Perfect! |
What? Why?
Closes #7120
Data migration to ensure any adjustments created without an order are re-associated with their order.
Included schema changes from running db:migrate in a separate commit; the formatting in
schema.rb
has changed a bit in Rails 5, so I wanted to keep the diffs separate.What should we test?
If we deploy to a staging server that has a couple of faulty adjustments, they should be fixed afterwards.
Release notes
Data migration to fix any adjustments missing an order id
Changelog Category: Technical changes