phorge-phorge/resources/sql/autopatches/20180306.opath.04.unique.sql

ALTER TABLE {$NAMESPACE}_owners.owners_path
  ADD UNIQUE KEY `key_path` (packageID, repositoryPHID, pathIndex);
Add a unique key to OwnersPath on "<packageID, repositoryPHID, pathIndex>" Summary: Depends on D19181. Ref T11015. This nukes duplicates from the table if they exist, then adds a unique key. (Duplicates should not exist and can not be added with any recent version of the web UI.) Test Plan: - Tried to add duplicates with web UI, didn't have any luck. - Explicitly added duplicates with manual `INSERT`s. - Viewed packages in web UI and saw duplicates. - Ran migrations, got a clean purge and a nice unique key. - There's still no way to actually hit a duplicate key error in the UI (unless you can collide hashes, I suppose), this is purely a correctness/robustness change. Maniphest Tasks: T11015 Differential Revision: https://secure.phabricator.com/D19182 2018-03-07 04:42:02 +01:00			`ALTER TABLE {$NAMESPACE}_owners.owners_path`
			ADD UNIQUE KEY `key_path` (packageID, repositoryPHID, pathIndex);