0fc9f9d3e7
DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
30 lines
822 B
Ruby
30 lines
822 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class FillAuthorizedProjects < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
class User < ActiveRecord::Base
|
|
self.table_name = 'users'
|
|
end
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = false
|
|
|
|
# We're not inserting any data so we don't need to start a transaction.
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
relation = User.select(:id)
|
|
.where('authorized_projects_populated IS NOT TRUE')
|
|
|
|
relation.find_in_batches(batch_size: 1_000) do |rows|
|
|
args = rows.map { |row| [row.id] }
|
|
|
|
Sidekiq::Client.push_bulk('class' => 'AuthorizedProjectsWorker', 'args' => args)
|
|
end
|
|
end
|
|
|
|
def down
|
|
end
|
|
end
|