epriestley d86506052c Update a very old Phriction migration which incorrectly uses "save()" ... Summary: See <https://discourse.phabricator-community.org/t/storage-upgrade-error/3748>. It is broadly unsafe for migrations to use "save()". If the object gains new fields later, the query will include "SET newField = X", which will fail against the old schema which is in the process of being upgraded. Instead, migrations must issue raw SQL against the schema as it is expected to exist at the time the migration executes. Migrations have followed this rule for a long time, but this ~6 year old migration was overlooked. Update it to issue a raw query to perform the policy update. Test Plan: This is somewhat flimsy since rebuilding a genuine reproduction case is messy, but used "bin/storage --apply ..." to at least get the new query to execute against modern Phabricator without issues. Subscribers: PHID-OPKG-gm6ozazyms6q6i22gyam Differential Revision: https://secure.phabricator.com/D21124		2020-04-15 08:06:30 -07:00
..
autopatches	Update a very old Phriction migration which incorrectly uses "save()"	2020-04-15 08:06:30 -07:00
patches	Make two ancient migrations fatal if they affect data	2019-02-06 17:08:34 -08:00
quickstart.sql	Update Quickstart SQL	2019-04-30 08:19:39 -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