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
29 lines
912 B
Ruby
29 lines
912 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class RemoveDuplicatesFromRoutes < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def up
|
|
# We can skip this migration when running a PostgreSQL database because
|
|
# we use an optimized query in the "FillProjectsRoutesTable" migration
|
|
# to fill these values that avoid duplicate entries in the routes table.
|
|
return unless Gitlab::Database.mysql?
|
|
|
|
execute <<-EOF
|
|
DELETE duplicated_rows.*
|
|
FROM routes AS duplicated_rows
|
|
INNER JOIN (
|
|
SELECT path, MAX(id) as max_id
|
|
FROM routes
|
|
GROUP BY path
|
|
HAVING COUNT(*) > 1
|
|
) AS good_rows ON good_rows.path = duplicated_rows.path AND good_rows.max_id <> duplicated_rows.id;
|
|
EOF
|
|
end
|
|
|
|
def down
|
|
end
|
|
end
|