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
22 lines
611 B
Ruby
22 lines
611 B
Ruby
# rubocop:disable Migration/UpdateLargeTable
|
|
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class MigrateUserProjectView < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = false
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
update_column_in_batches(:users, :project_view, 2) do |table, query|
|
|
query.where(table[:project_view].eq(0))
|
|
end
|
|
end
|
|
|
|
def down
|
|
# Nothing can be done to restore old values
|
|
end
|
|
end
|