Dropping columns in a rails migration is such a big foot gun. If you follow all the guides and stack overflow answers, you will break your production application during deploys.
-
-
Yes, the issue is dropping a column during a migration, and existing processes reference that column due to cache so will proceed to write bad queries and 500
-
This is why zero downtime deploys aren't the panacea everyone thinks they are. If you have a migration and care about breaking prod, you need a maintenance window or a strategy for keeping old clients working across the deploy.
-
We have to have 99.99% uptime with some customers so downtime on deploys is not an option.
-
Then you need a strategy for straddling releases. Like the big API boys
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.