-
Notifications
You must be signed in to change notification settings - Fork 19
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
Change invoices.issue_date
database column to NOT NULL
#1107
Conversation
81bba94
to
5528697
Compare
5528697
to
5a83019
Compare
deployment failed on staging due to null issue_date values. All the issue_date columen values are empty for that matter so apparently populate_invoice_issue_date was not run
|
Then run it, what's the problem? |
5a83019
to
3a97eb9
Compare
I cannot as db is replaced with every deployment so this migration should be run in the deployment process prior to removing it |
Then talk to @ratM1n to switch to fixtures (test data we use for testing). I briefly explained him a point of them. I could assist further, if you are OK to migrate. https://guides.rubyonrails.org/testing.html#the-low-down-on-fixtures P.S. I wonder how #1013 was tested if you say it's impossible to run that data migration. |
3a97eb9
to
30ea880
Compare
not able to deploy |
How can I help? |
@ratM1n Confirmed it's now in working state. |
populate_invoice_issue_date
data migration is run against every deployment, since this change removes it!Closes #1008