Introduce database table for user highest roles
What does this MR do?
Part of #118592 (closed)
Introduce new database table to store highest role per User they have in a Group or a Project. If a User has an open invite or pending access request or no membership the highest role will be set to nil.
This is a suggestion from this comment in order to resolve performance issues when querying too much data.
Example
| user_id | highest_role | updated_at |
|---|---|---|
| 10 | 50 | 2020-03-11 09:40:00 |
| 11 | 20 | 2020-03-11 09:40:00 |
| 12 | null | 2020-03-11 10:05:00 |
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team