Page MenuHomePhabricator

Migrate revision storage to modern status constants ("accepted") instead of legacy numeric values ("2")
ClosedPublic

Authored by epriestley on Aug 11 2017, 11:34 PM.
Tags
None
Referenced Files
F19941265: D18418.id.diff
Wed, Apr 15, 9:31 AM
F19933381: D18418.id44262.diff
Sat, Apr 11, 1:01 AM
F19914620: D18418.diff
Fri, Apr 3, 1:15 PM
F19914617: D18418.diff
Fri, Apr 3, 1:10 PM
F19912191: D18418.diff
Thu, Apr 2, 5:40 PM
F19907971: D18418.id44262.diff
Wed, Apr 1, 3:09 PM
F19907969: D18418.id44262.diff
Wed, Apr 1, 3:09 PM
F19508180: D18418.id44262.diff
Jan 10 2026, 1:55 AM
Subscribers
None

Details

Summary

Ref T2543. Rewrites all the storage to use constants.

Note that transactions still use legacy values, I'll migrate and update them separately.

Test Plan
  • Ran migration.
  • Browsed around, changed revision states, viewed dashboard, etc.
  • Selected DISTINCT() and GROUP_CONCAT() of the status field in the database, saw sane/expected before and after values.
  • Verified that old Conduit methods still return numeric constants for compatibility.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable