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
F19072122: D18418.id.diff
Nov 30 2025, 9:28 PM
F19060469: D18418.diff
Nov 29 2025, 9:21 AM
F18934419: D18418.id44262.diff
Nov 10 2025, 3:02 PM
F18846840: D18418.id.diff
Oct 29 2025, 9:24 PM
F18841472: D18418.diff
Oct 28 2025, 9:23 AM
F18815397: D18418.id44253.diff
Oct 21 2025, 2:00 AM
F18812350: D18418.diff
Oct 20 2025, 8:45 AM
F18759165: D18418.id.diff
Oct 6 2025, 2:12 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