Page MenuHomePhabricator

Migrate project profiles onto projects, and remove ProjectProfile object
ClosedPublic

Authored by epriestley on Feb 10 2014, 8:37 PM.
Tags
None
Referenced Files
F13248434: D8183.id.diff
Fri, May 24, 2:39 AM
F13206795: D8183.id.diff
Wed, May 15, 5:41 PM
F13183611: D8183.id18524.diff
Fri, May 10, 10:34 AM
F13183610: D8183.id18507.diff
Fri, May 10, 10:34 AM
F13183280: D8183.id.diff
Fri, May 10, 8:05 AM
F13183222: D8183.diff
Fri, May 10, 7:39 AM
Unknown Object (File)
Tue, May 7, 6:34 AM
Unknown Object (File)
Fri, May 3, 1:41 AM
Subscribers

Details

Summary

Ref T4379. Long ago, the "Project" vs "ProjectProfile" split was intended to allow a bunch of special fields on projects without burdening the simple use cases, but CustomField handles that far better and far more generally, and doing this makes using ApplicationTransactions a pain to get right, so get rid of it.

The only remaining field is profileImagePHID, which we can just move to the main Project object. This is custom enough that I think it's reasonable not to express it as a custom field.

Test Plan

Created a project, set profile, edited project, viewed in typeahead, ran migration, verified database results.

Diff Detail

Repository
rP Phabricator
Branch
projsub9
Lint
Lint Passed
Unit
No Test Coverage

Event Timeline

are you going to drop the project_profile table in a future diff?

Yeah -- I'm probably going to do the [Later] ... thing just so we aren't outright destroying data in case the migrations are bogus, but this table is pretty low risk. If it didn't have the descriptions in it I'd just drop it outright.