![Jan Provaznik](/assets/img/avatar_default.png)
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
1.1 KiB
Ruby
30 lines
1.1 KiB
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class FillProjectsRoutesTable < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = true
|
|
DOWNTIME_REASON = 'No new projects should be created during data copy'
|
|
|
|
def up
|
|
if Gitlab::Database.postgresql?
|
|
execute <<-EOF
|
|
INSERT INTO routes (source_id, source_type, path)
|
|
(SELECT DISTINCT ON (namespaces.path, projects.path) projects.id, 'Project', concat(namespaces.path, '/', projects.path)
|
|
FROM projects INNER JOIN namespaces ON projects.namespace_id = namespaces.id
|
|
ORDER BY namespaces.path, projects.path, projects.id DESC)
|
|
EOF
|
|
else
|
|
execute <<-EOF
|
|
INSERT INTO routes (source_id, source_type, path)
|
|
(SELECT projects.id, 'Project', concat(namespaces.path, '/', projects.path)
|
|
FROM projects INNER JOIN namespaces ON projects.namespace_id = namespaces.id)
|
|
EOF
|
|
end
|
|
end
|
|
|
|
def down
|
|
execute("DELETE FROM routes WHERE source_type = 'Project'")
|
|
end
|
|
end
|