1ab33b15d1
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. |
||
---|---|---|
.. | ||
add_column.rb | ||
add_concurrent_foreign_key.rb | ||
add_concurrent_index.rb | ||
add_index.rb | ||
add_timestamps.rb | ||
datetime.rb | ||
hash_index.rb | ||
remove_column.rb | ||
remove_concurrent_index.rb | ||
remove_index.rb | ||
reversible_add_column_with_default.rb | ||
safer_boolean_column.rb | ||
timestamps.rb | ||
update_column_in_batches.rb | ||
update_large_table.rb |