Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api | ||
ci/api | ||
projects | ||
git_http_spec.rb | ||
jwt_controller_spec.rb | ||
lfs_http_spec.rb | ||
openid_connect_spec.rb | ||
request_profiler_spec.rb |
BigW Consortium Gitlab
Having two states that essentially mean the same thing is very much like having a boolean "true" and boolean "mostly-true": it's rather silly. This commit merges the "reopened" state into the "opened" state while taking care of system notes still showing messages along the lines of "Alice reopened this issue". A big benefit from having only two states (opened and closed) is that indexing and querying becomes simpler and more performant. For example, to get all the opened queries we no longer have to query both states: SELECT * FROM issues WHERE project_id = 2 AND state IN ('opened', 'reopened'); Instead we can query a single state directly, which can be much faster: SELECT * FROM issues WHERE project_id = 2 AND state = 'opened'; Further, only having two states makes indexing easier as we will only ever filter (and thus scan an index) using a single value. Partial indexes could help but aren't supported on MySQL, complicating the development process and not being helpful for MySQL.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api | Loading commit data... | |
ci/api | Loading commit data... | |
projects | Loading commit data... | |
git_http_spec.rb | Loading commit data... | |
jwt_controller_spec.rb | Loading commit data... | |
lfs_http_spec.rb | Loading commit data... | |
openid_connect_spec.rb | Loading commit data... | |
request_profiler_spec.rb | Loading commit data... |