epriestley 0a77b0e53e Work around an issue in MariaDB where dropping a column from a UNIQUE KEY fails ... Summary: See T13193. See T13077. If we drop a column which is part of a UNIQUE KEY, MariaDB raises an error. This is probably a bad idea on our side anyway, but in this case it wasn't an obviously bad idea. To get around this: - Drop the unique key, if it exists, before dropping the column. - Explicitly add the new unique key afterward. Test Plan: Ran `bin/storage upgrade` locally without issue, but I'm on MySQL. Will follow up on T13193. Reviewers: amckinley Subscribers: PHID-OPKG-gm6ozazyms6q6i22gyam Differential Revision: https://secure.phabricator.com/D19624		2018-08-30 06:25:39 -07:00
..
autopatches	Work around an issue in MariaDB where dropping a column from a UNIQUE KEY fails	2018-08-30 06:25:39 -07:00
patches	Remove a very old Herald garbage collection migration	2018-01-26 10:54:37 -08:00
quickstart.sql	Revert quickstart for tables with native FULLTEXT indexes to MyISAM	2017-09-12 12:24:23 -07:00
stopwords.txt	Provide a setup warning about using the default MySQL stopword file	2014-08-13 15:34:09 -07:00
stopwords_myisam.txt	Show users how fulltext search queries are parsed and executed; don't query stopwords or short tokens	2017-04-12 19:07:54 -07:00