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
..
builtin	Dynamically composite favicons from customizable sources	2018-03-12 15:28:41 -07:00
celerity	Add a UI element for navigating between versions of a Phriction document	2018-08-29 13:49:15 -07:00
cows	Use PHP implementation of Cowsay for cowsay rule	2015-09-13 12:27:30 -07:00
emoji	Add aliases for "party" emoji (🎉)	2018-02-05 12:23:26 -08:00
figlet/custom	Include "Figlet" and PEAR "Text_Figlet" in externals	2015-09-13 12:30:48 -07:00
font	Made Meme Generator	2013-01-19 18:43:43 -08:00
sprite	Uh, update Phabricator login image	2017-08-11 13:37:26 -07:00
sql	Work around an issue in MariaDB where dropping a column from a UNIQUE KEY fails	2018-08-30 06:25:39 -07:00
sshd	Drop interactive login from sshd example	2017-06-27 12:51:46 -07:00