crm/database/migrations/20220604103833_update_relation_to_permission_table.php

<?php

use think\migration\Migrator;
use \app\model\Permission;
use \app\model\Grant;
use think\migration\db\Column;

class UpdateRelationToPermissionTable extends Migrator
{
    /**
     * Change Method.
     *
     * Write your reversible migrations using this method.
     *
     * More information on writing migrations is available here:
     * http://docs.phinx.org/en/latest/migrations.html#the-abstractmigration-class
     *
     * The following commands can be used in this method and Phinx will
     * automatically reverse them when rolling back:
     *
     *    createTable
     *    renameTable
     *    addColumn
     *    renameColumn
     *    addIndex
     *    addForeignKey
     *
     * Remember to call "create()" or "update()" and NOT "save()" when working
     * with the Table class.
     */
    public function change()
    {

        $parent_id = (new Permission())->where('auth_name', '=', '装修拼团')->value('id');
        if(!empty($parent_id)){
            $ms = (new Permission())->where('id', '=', $parent_id)->update(array('uri'=>'spellgroup/set','relation'=>'spellgroup/set,spellgroup/addSave,spellgroup/team_list,spellgroup/sel_team_detail'));
            if($ms){
            $grant = Grant::where('name', '=', '超级管理员')->select();
            foreach ($grant as $k => $v) {
                $permission = array_merge(json_decode(json_encode($v->permission), true), [intval($parent_id)]);
                asort($permission);
                $v->permission = array_values(array_filter(array_unique($permission)));
                $v->save();
            }
            }
        }
        
    }
}