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
F14478230: D8183.diff
Sat, Dec 28, 4:57 PM
Unknown Object (File)
Fri, Dec 13, 5:43 AM
Unknown Object (File)
Nov 26 2024, 9:56 PM
Unknown Object (File)
Nov 26 2024, 3:54 PM
Unknown Object (File)
Nov 22 2024, 6:33 PM
Unknown Object (File)
Nov 18 2024, 10:33 AM
Unknown Object (File)
Nov 15 2024, 11:06 PM
Unknown Object (File)
Nov 14 2024, 10:35 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.