archive/phabricator
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Make Phriction policy migration even more robust

Browse Source 
We have at least one project with `null` as a viewPolicy. This should get
sorted out separately, but make the migration robust against it.

Auditors: btrahan
This commit is contained in:
epriestley
2014-11-07 15:44:19 -08:00
parent 3d44941373
commit 2e13a31722
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
resources/sql/autopatches/20141107.phriction.policy.2.php
View File

@@ -28,10 +28,14 @@ foreach (new LiskMigrationIterator($table) as $doc) {
->executeOne(); ->executeOne();
if ($project) { if ($project) {
$view_policy = nonempty($project->getViewPolicy(), $default_view_policy);
$edit_policy = nonempty($project->getEditPolicy(), $default_edit_policy);
$project_name = $project->getName(); $project_name = $project->getName();
echo "Migrating doc $id to project policy $project_name...\n"; echo "Migrating doc $id to project policy $project_name...\n";
$doc->setViewPolicy($project->getViewPolicy()); $doc->setViewPolicy($view_policy);
$doc->setEditPolicy($project->getEditPolicy()); $doc->setEditPolicy($edit_policy);
$doc->save(); $doc->save();
continue; continue;
} }