gitlab-org--gitlab-foss/db/migrate/20161018124658_make_project...

# rubocop:disable Migration/UpdateColumnInBatches
class MakeProjectOwnersMasters < ActiveRecord::Migration[4.2]
  include Gitlab::Database::MigrationHelpers

  DOWNTIME = false

  disable_ddl_transaction!

  def up
    update_column_in_batches(:members, :access_level, 40) do |table, query|
      query.where(table[:access_level].eq(50).and(table[:source_type].eq('Project')))
    end
  end

  def down
    # do nothing
  end
end
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`
Add version 4.2 to all existing migrations 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 2018-11-13 07:27:31 +00:00			`class MakeProjectOwnersMasters < ActiveRecord::Migration[4.2]`
Fix project member access levels 2016-10-18 13:49:19 +00:00			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

Disable transactions in migrations that should not use it 2017-06-21 12:35:06 +00:00			`disable_ddl_transaction!`

Fix project member access levels 2016-10-18 13:49:19 +00:00			`def up`
			`update_column_in_batches(:members, :access_level, 40) do \|table, query\|`
			`query.where(table[:access_level].eq(50).and(table[:source_type].eq('Project')))`
			`end`
			`end`

			`def down`
			`# do nothing`
			`end`
			`end`