gitlab-org--gitlab-foss/changelogs/unreleased/sh-enforce-unique-and-not-null-project-ids-project-features.yml

---
title: Add a unique and not null constraint on the project_features.project_id column
merge_request:
author:
type: fixed
Add a unique and not null constraint on the project_features.project_id column This commit has two migrations: 1. The first prunes duplicate rows in the project_features table and leaves the row with the highest ID. Since the behavior was indeterministic before and depended on which row the database decided to use, this change at least makes the permissions consistent. For example, in some cases, the Wiki may have been disabled but enabled in another entry. 2. The second adds a non-null constraint on the project_features.project_id column. Closes #37882 Fixes a significant part of gitlab-com/migration#408. We found that we were overcounting Wikis because of these duplicates. On GitLab.com, there are 56 rows with duplicate entries by project_id, and 16,661 rows with NULL project_id values. 2018-05-11 14:19:49 -04:00			`---`
			`title: Add a unique and not null constraint on the project_features.project_id column`
			`merge_request:`
			`author:`
			`type: fixed`