rubocop/cop/migration · 8d691856aed9c99b0728925a5c3815cc76f545b8 · Forest Godfrey / gitlab-ce

Add cop for use of remove_column · 1ab33b15

authored Dec 11, 2017

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.

1ab33b15

Name	Last commit	Last update
..
add_column.rb		Loading commit data...
add_concurrent_foreign_key.rb		Loading commit data...
add_concurrent_index.rb		Loading commit data...
add_index.rb		Loading commit data...
add_timestamps.rb		Loading commit data...
datetime.rb		Loading commit data...
hash_index.rb		Loading commit data...
remove_column.rb		Loading commit data...
remove_concurrent_index.rb		Loading commit data...
remove_index.rb		Loading commit data...
reversible_add_column_with_default.rb		Loading commit data...
safer_boolean_column.rb		Loading commit data...
timestamps.rb		Loading commit data...
update_column_in_batches.rb		Loading commit data...
update_large_table.rb		Loading commit data...