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
F17934350: D18418.id.diff
Wed, Jul 30, 10:17 PM
F17903852: D18418.diff
Tue, Jul 29, 11:10 AM
F17849776: D18418.id.diff
Sun, Jul 27, 9:05 AM
F17846319: D18418.id44253.diff
Sun, Jul 27, 4:42 AM
F17815301: D18418.diff
Fri, Jul 25, 9:51 PM
Unknown Object (File)
Jun 28 2025, 10:22 AM
Unknown Object (File)
May 31 2025, 9:11 PM
Unknown Object (File)
May 31 2025, 11:01 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