Cache the presence of an issue_tracker at project level (!4466) · Merge requests · GitLab.org / GitLab FOSS · GitLab

Do not update/delete: Banner broadcast message test data

Do not update/delete: Notification broadcast message test data

Paco Guzman requested to merge 18027-cache-project-external_issue_tracker into master Jun 03, 2016

What does this MR do?

Cache in the database the presence of an external issue tracker for a project

Are there points in the code the reviewer needs to double check?

Migration mainly (to support PostgreSQL and MySQL). We're setting false as default value and then executing a SQL query we update to true for the projects that has a external issue tracker. Do you think we need to execute that query on batches like the column default does?

Why was this MR needed?

To reduce the number of database queries

What are the relevant issue numbers?

#18027 (closed)