Page MenuHomePhabricator

Make two ancient migrations fatal if they affect data
ClosedPublic

Authored by epriestley on Feb 6 2019, 4:57 PM.
Tags
None
Referenced Files
F15520055: D20107.id48031.diff
Sun, Apr 20, 2:57 AM
F15520053: D20107.id.diff
Sun, Apr 20, 2:56 AM
F15520051: D20107.id48015.diff
Sun, Apr 20, 2:56 AM
F15516229: D20107.id48031.diff
Fri, Apr 18, 5:29 PM
F15454670: D20107.id.diff
Sat, Mar 29, 7:41 PM
F15442889: D20107.id48031.diff
Thu, Mar 27, 1:08 AM
F15435642: D20107.id48016.diff
Mar 25 2025, 9:28 AM
F15432282: D20107.diff
Mar 24 2025, 5:16 PM
Subscribers
Restricted Owners Package

Details

Summary

Depends on D20106. Ref T6703. Since I plan to change the ExternalAccount table, these migrations (which rely on save()) will stop working.

They could be rewritten to use raw queries, but I suspect few or no installs are affected. At least for now, just make them safe: if they would affect data, fatal and tell the user to perform a more gradual upgrade.

Also remove an ALTER IGNORE TABLE (this syntax was removed at some point) and fix a %Q when adjusting certain types of primary keys.

Test Plan

Ran bin/storage upgrade --no-quickstart --force --namespace test1234 to get a complete migration since the beginning of time.

Diff Detail

Repository
rP Phabricator
Branch
welcome10
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 21856
Build 29825: Run Core Tests
Build 29824: arc lint + arc unit