BigW Consortium Gitlab
Precalculate authorized projects in database ## What does this MR do? It caches user's authorized projects in database instead of using multiple unions, which should simplify and speed-up things since this operation (getting authorized projects) is used a lot. ## Are there points in the code the reviewer needs to double check? Did we miss a scenario where we need to refresh the list of projects? ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [ ] ~~[Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)~~ - [ ] ~~API support added~~ - Tests - [x] Added for this feature/bug - [x] All builds are passing - [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if it does - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? #23150 See merge request !6839
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
01_admin.rb | Loading commit data... | |
04_project.rb | Loading commit data... | |
05_users.rb | Loading commit data... | |
06_teams.rb | Loading commit data... | |
07_milestones.rb | Loading commit data... | |
09_issues.rb | Loading commit data... | |
10_merge_requests.rb | Loading commit data... | |
11_keys.rb | Loading commit data... | |
12_snippets.rb | Loading commit data... | |
13_comments.rb | Loading commit data... | |
14_pipelines.rb | Loading commit data... | |
15_award_emoji.rb | Loading commit data... | |
16_protected_branches.rb | Loading commit data... | |
17_cycle_analytics.rb | Loading commit data... |