From eb086a4bfd2495168483a2652571f247e6b768a5 Mon Sep 17 00:00:00 2001 From: Sean McGivern Date: Tue, 19 Jun 2018 17:18:15 +0100 Subject: Disallow methods that copy data on large tables {change_column_type,rename_column}_concurrently both copy data from one column to another during a migration, which should not be done on GitLab.com. Instead, we should use background migrations. --- rubocop/cop/migration/update_large_table.rb | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'rubocop') diff --git a/rubocop/cop/migration/update_large_table.rb b/rubocop/cop/migration/update_large_table.rb index bb14d0f4f56..e3e3de0a4d7 100644 --- a/rubocop/cop/migration/update_large_table.rb +++ b/rubocop/cop/migration/update_large_table.rb @@ -34,8 +34,15 @@ module RuboCop users ].freeze + BATCH_UPDATE_METHODS = %w[ + :add_column_with_default + :change_column_type_concurrently + :rename_column_concurrently + :update_column_in_batches + ].join(' ').freeze + def_node_matcher :batch_update?, <<~PATTERN - (send nil? ${:add_column_with_default :update_column_in_batches} $(sym ...) ...) + (send nil? ${#{BATCH_UPDATE_METHODS}} $(sym ...) ...) PATTERN def on_send(node) -- cgit v1.2.1