BigW Consortium Gitlab
remove_column should only be used in the up (or change) step of a migration if it's a post-deployment migration. Otherwise there will be downtime due to the ActiveRecord column cache, which we can avoid by using the IgnorableColumn concern in combination with a post-deployment migration.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
migration | Loading commit data... | |
rspec | Loading commit data... | |
active_record_dependent.rb | Loading commit data... | |
active_record_serialize.rb | Loading commit data... | |
custom_error_class.rb | Loading commit data... | |
gem_fetcher.rb | Loading commit data... | |
in_batches.rb | Loading commit data... | |
line_break_after_guard_clauses.rb | Loading commit data... | |
polymorphic_associations.rb | Loading commit data... | |
project_path_helper.rb | Loading commit data... | |
redirect_with_status.rb | Loading commit data... |