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
1.1 KiB
Ruby
38 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 PrecalculateTrendingProjects < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def up
|
|
create_table :trending_projects do |t|
|
|
t.references :project, index: true, foreign_key: { on_delete: :cascade }, null: false
|
|
end
|
|
|
|
timestamp = connection.quote(1.month.ago)
|
|
|
|
# We're hardcoding the visibility level (public) here so that if it ever
|
|
# changes this query doesn't suddenly use the new value (which may break
|
|
# later migrations).
|
|
visibility = 20
|
|
|
|
execute <<-EOF.strip_heredoc
|
|
INSERT INTO trending_projects (project_id)
|
|
SELECT project_id
|
|
FROM notes
|
|
INNER JOIN projects ON projects.id = notes.project_id
|
|
WHERE notes.created_at >= #{timestamp}
|
|
AND notes.system IS FALSE
|
|
AND projects.visibility_level = #{visibility}
|
|
GROUP BY project_id
|
|
ORDER BY count(*) DESC
|
|
LIMIT 100;
|
|
EOF
|
|
end
|
|
|
|
def down
|
|
drop_table :trending_projects
|
|
end
|
|
end
|