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
38 lines
824 B
Ruby
38 lines
824 B
Ruby
class RenameDuplicatedVariableKey < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
execute(<<~SQL)
|
|
UPDATE ci_variables
|
|
SET #{key} = CONCAT(#{key}, #{underscore}, id)
|
|
WHERE id IN (
|
|
SELECT *
|
|
FROM ( -- MySQL requires an extra layer
|
|
SELECT dup.id
|
|
FROM ci_variables dup
|
|
INNER JOIN (SELECT max(id) AS id, #{key}, project_id
|
|
FROM ci_variables tmp
|
|
GROUP BY #{key}, project_id) var
|
|
USING (#{key}, project_id) where dup.id <> var.id
|
|
) dummy
|
|
)
|
|
SQL
|
|
end
|
|
|
|
def down
|
|
# noop
|
|
end
|
|
|
|
def key
|
|
# key needs to be quoted in MySQL
|
|
quote_column_name('key')
|
|
end
|
|
|
|
def underscore
|
|
quote('_')
|
|
end
|
|
end
|