gitlab-org--gitlab-foss/db/post_migrate/20170131214021_reset_users_...

# rubocop:disable Migration/UpdateLargeTable
# rubocop:disable Migration/UpdateColumnInBatches
class ResetUsersAuthorizedProjectsPopulated < ActiveRecord::Migration
  include Gitlab::Database::MigrationHelpers

  DOWNTIME = false

  disable_ddl_transaction!

  def up
    # This ensures we don't lock all users for the duration of the migration.
    update_column_in_batches(:users, :authorized_projects_populated, nil)
  end

  def down
    # noop
  end
end
Prevent update_column_in_batches on large tables add_column_with_default is implemented in terms of update_column_in_batches, but update_column_in_batches can be used independently. Neither of these should be used on the specified large tables, because they will cause issues on large instances like GitLab.com. This also ignores the cop for all existing migrations, renaming AddColumnWithDefaultToLargeTable where appropriate. 2017-11-17 13:38:14 +00:00			`# rubocop:disable Migration/UpdateLargeTable`
Disable Migration/UpdateColumnInBatches for old migrations Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-05-23 12:57:03 +00:00			`# rubocop:disable Migration/UpdateColumnInBatches`
Trigger refreshing of permissions in a migration This migration resets `users.authorized_projects_populated` (in batches) so that active users' permissions are refreshed on the next request. This ensures that their permissions are properly stored. 2017-01-31 21:44:31 +00:00			`class ResetUsersAuthorizedProjectsPopulated < ActiveRecord::Migration`
			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

			`disable_ddl_transaction!`

			`def up`
			`# This ensures we don't lock all users for the duration of the migration.`
			`update_column_in_batches(:users, :authorized_projects_populated, nil)`
			`end`

			`def down`
			`# noop`
			`end`
			`end`