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
27 lines
840 B
Ruby
27 lines
840 B
Ruby
# frozen_string_literal: true
|
|
|
|
class RecalculateSiteStatistics < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
transaction do
|
|
execute('SET LOCAL statement_timeout TO 0') if Gitlab::Database.postgresql? # see https://gitlab.com/gitlab-org/gitlab-ce/issues/48967
|
|
|
|
execute("UPDATE site_statistics SET repositories_count = (SELECT COUNT(*) FROM projects)")
|
|
end
|
|
|
|
transaction do
|
|
execute('SET LOCAL statement_timeout TO 0') if Gitlab::Database.postgresql? # see https://gitlab.com/gitlab-org/gitlab-ce/issues/48967
|
|
|
|
execute("UPDATE site_statistics SET wikis_count = (SELECT COUNT(*) FROM project_features WHERE wiki_access_level != 0)")
|
|
end
|
|
end
|
|
|
|
def down
|
|
# No downside in keeping the counter up-to-date
|
|
end
|
|
end
|