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_concurrent_foreign_key_spec.rb | ||
| add_concurrent_index_spec.rb | ||
| add_timestamps_spec.rb | ||
| datetime_spec.rb | ||
| hash_index_spec.rb | ||
| remove_column_spec.rb | ||
| remove_concurrent_index_spec.rb | ||
| remove_index_spec.rb | ||
| reversible_add_column_with_default_spec.rb | ||
| safer_boolean_column_spec.rb | ||
| timestamps_spec.rb | ||
| update_column_in_batches_spec.rb | ||
| update_large_table_spec.rb | ||