GetModel 获取单个数据

条件查询:请求可使用 id 或 where 字段进行查询,二者选一即可

  • id int|string
  • where array,必须使用数组方式来定义
  1. $this->post['where'] = [
  2. ['name', '=', 'van']
  3. ];

引入特性,需要定义必须的操作模型 model

  1. use think\bit\traits\GetModel;
  2. class AdminClass extends Base {
  3. use GetModel;
  4. protected $model = 'admin';
  5. }

自定义获取验证器为 get_validate,默认为

  1. protected $get_validate = [
  2. 'id' => 'require'
  3. ];

也可以在控制器中针对性修改

  1. use think\bit\traits\GetModel;
  2. class AdminClass extends Base {
  3. use GetModel;
  4. protected $model = 'admin';
  5. protected $get_validate = [
  6. 'id' => 'require',
  7. 'name' => 'require'
  8. ];
  9. }

判断是否有前置处理,则需要调用生命周期 GetBeforeHooks

  1. use think\bit\traits\GetModel;
  2. use think\bit\lifecycle\GetBeforeHooks;
  3. class AdminClass extends Base implements GetBeforeHooks {
  4. use GetModel;
  5. protected $model = 'admin';
  6. public function __getBeforeHooks()
  7. {
  8. return true;
  9. }
  10. }

__getBeforeHooks 的返回值为 false 则在此结束执行,并返回 get_before_result 属性的值,默认为:

  1. protected $get_before_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:before_fail'
  4. ];

在生命周期函数中可以通过重写自定义前置返回

  1. use think\bit\traits\GetModel;
  2. use think\bit\lifecycle\GetBeforeHooks;
  3. class AdminClass extends Base implements GetBeforeHooks {
  4. use GetModel;
  5. protected $model = 'admin';
  6. public function __getBeforeHooks()
  7. {
  8. $this->get_before_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:only'
  11. ];
  12. return false;
  13. }
  14. }

如需要给接口在后端就设定固定条件,只需要重写 get_condition,默认为

  1. protected $get_condition = [];

例如加入企业主键限制

  1. use think\bit\traits\GetModel;
  2. class AdminClass extends Base {
  3. use GetModel;
  4. protected $model = 'admin';
  5. protected $get_condition = [
  6. ['enterprise', '=', 1]
  7. ];
  8. }

如需要给接口限制返回字段,只需要重写 get_field,默认为

  1. protected $get_field = ['update_time,create_time', true];

例如返回除 update_time 修改时间所有的字段

  1. use think\bit\traits\GetModel;
  2. class AdminClass extends Base {
  3. use GetModel;
  4. protected $model = 'admin';
  5. protected $get_field = ['update_time', true];
  6. }

如自定义返回结果,则需要调用生命周期 GetCustom

  1. use think\bit\traits\GetModel;
  2. use think\bit\lifecycle\GetCustom;
  3. class AdminClass extends Base implements GetCustom {
  4. use GetModel;
  5. protected $model = 'admin';
  6. public function __getCustomReturn($data)
  7. {
  8. return [
  9. 'error' => 0,
  10. 'data' => $data
  11. ];
  12. }
  13. }

__getCustomReturn 需要返回整体的响应结果

  1. return [
  2. 'error' => 0,
  3. 'data' => $data
  4. ];
  • data array 原数据

OriginListsModel 获取列表数据

条件合并: 请求中的 where 将于 origin_lists_condition 合并

  • where array 必须使用数组方式来定义
  1. $this->post['where'] = [
  2. ['name', 'like', '%v%']
  3. ];

模糊查询在 post 请求中加入参数 like,他将于以上条件共同合并

  • like array 模糊搜索条件
    • field 模糊搜索字段名
    • value 模糊搜索字段值
  1. [{ "field": "name", "value": "a" }]

引入特性需要定义必须的操作模型 model

  1. use think\bit\traits\OriginListsModel;
  2. class AdminClass extends Base {
  3. use OriginListsModel;
  4. protected $model = 'admin';
  5. }

合并模型验证器下 origin 场景,所以需要对应创建验证器场景 validate/AdminClass, 并加入场景 origin

  1. use think\Validate;
  2. class AdminClass extends Validate
  3. {
  4. protected $rule = [
  5. 'status' => 'require',
  6. ];
  7. protected $scene = [
  8. 'origin' => ['status'],
  9. ];
  10. }

可定义固定条件属性 $this->origin_lists_condition,默认为 []

  1. use think\bit\traits\OriginListsModel;
  2. class NoBodyClass extends Base {
  3. use OriginListsModel;
  4. protected $model = 'nobody';
  5. protected $origin_lists_condition = [
  6. ['status', '=', 1]
  7. ];
  8. }

如果接口的查询条件较为特殊,可以重写 origin_lists_condition_query

  1. use think\bit\traits\OriginListsModel;
  2. class NoBodyClass extends Base {
  3. use OriginListsModel;
  4. protected $model = 'nobody';
  5. public function __construct(App $app = null)
  6. {
  7. parent::__construct($app);
  8. $this->origin_lists_condition_query = function (Query $query) {
  9. $query->whereOr([
  10. 'type' => 1
  11. ]);
  12. };
  13. }
  14. }

如自定义前置处理,则需要调用生命周期 OriginListsBeforeHooks

  1. use think\bit\traits\OriginListsModel;
  2. use think\bit\lifecycle\OriginListsBeforeHooks;
  3. class AdminClass extends Base implements OriginListsBeforeHooks {
  4. use OriginListsModel;
  5. protected $model = 'admin';
  6. public function __originListsBeforeHooks()
  7. {
  8. return true;
  9. }
  10. }

__originListsBeforeHooks 的返回值为 false 则在此结束执行,并返回 origin_lists_before_result 属性的值,默认为:

  1. protected $origin_lists_before_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:before_fail'
  4. ];

在生命周期函数中可以通过重写自定义前置返回

  1. use think\bit\traits\OriginListsModel;
  2. use think\bit\lifecycle\OriginListsBeforeHooks;
  3. class AdminClass extends Base implements OriginListsBeforeHooks {
  4. use OriginListsModel;
  5. protected $model = 'admin';
  6. public function __originListsBeforeHooks()
  7. {
  8. $this->origin_lists_before_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:only'
  11. ];
  12. return false;
  13. }
  14. }

如需要给接口在后端就设定固定条件,只需要重写 origin_lists_condition,默认为

  1. protected $origin_lists_condition = [];

例如加入企业主键限制

  1. use think\bit\traits\OriginListsModel;
  2. class AdminClass extends Base {
  3. use OriginListsModel;
  4. protected $model = 'admin';
  5. protected $origin_lists_condition = [
  6. ['enterprise', '=', 1]
  7. ];
  8. }

如果需要列表按条件排序,只需要重写 origin_lists_orders,默认为

  1. protected $origin_lists_orders = 'create_time desc';

例如按年龄进行排序

  1. use think\bit\traits\OriginListsModel;
  2. class AdminClass extends Base {
  3. use OriginListsModel;
  4. protected $model = 'admin';
  5. protected $origin_lists_orders = 'age desc';
  6. }

如需要给接口限制返回字段,只需要重写 origin_lists_field,默认为

  1. protected $origin_lists_field = ['update_time,create_time', true];

例如返回除 update_time 修改时间所有的字段

  1. use think\bit\traits\OriginListsModel;
  2. class AdminClass extends Base {
  3. use OriginListsModel;
  4. protected $model = 'admin';
  5. protected $origin_lists_field = ['update_time', true];
  6. }

如自定义返回结果,则需要调用生命周期 OriginListsCustom

  1. use think\bit\traits\OriginListsModel;
  2. use think\bit\lifecycle\OriginListsCustom;
  3. class AdminClass extends Base implements OriginListsCustom {
  4. use OriginListsModel;
  5. protected $model = 'admin';
  6. public function __originListsCustomReturn(Array $lists)
  7. {
  8. return [
  9. 'error' => 0,
  10. 'data' => $lists
  11. ];
  12. }
  13. }

__originListsCustomReturn 需要返回整体的响应结果

  1. return [
  2. 'error' => 0,
  3. 'data' => $data
  4. ];
  • data array 原数据

ListsModel 获取分页数据

条件合并: 请求中的 where 将于 lists_condition 合并

  • where array 必须使用数组方式来定义
  1. $this->post['where'] = [
  2. ['name', '=', 'van']
  3. ];

引入特性,需要定义必须的操作模型 model

  1. use think\bit\traits\ListsModel;
  2. class AdminClass extends Base {
  3. use ListsModel;
  4. protected $model = 'admin';
  5. }

如自定义前置处理,则需要调用生命周期 ListsBeforeHooks

  1. use think\bit\traits\ListsModel;
  2. use think\bit\lifecycle\ListsBeforeHooks;
  3. class AdminClass extends Base implements ListsBeforeHooks {
  4. use ListsModel;
  5. protected $model = 'admin';
  6. public function __listsBeforeHooks()
  7. {
  8. return true;
  9. }
  10. }

__listsBeforeHooks 的返回值为 false 则在此结束执行,并返回 lists_before_result 属性的值,默认为:

  1. protected $lists_before_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:before_fail'
  4. ];

在生命周期函数中可以通过重写自定义前置返回

  1. use think\bit\traits\ListsModel;
  2. use think\bit\lifecycle\ListsBeforeHooks;
  3. class AdminClass extends Base implements ListsBeforeHooks {
  4. use ListsModel;
  5. protected $model = 'admin';
  6. public function __listsBeforeHooks()
  7. {
  8. $this->lists_before_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:only'
  11. ];
  12. return false;
  13. }
  14. }

如需要给接口在后端就设定固定条件,只需要重写 lists_condition,默认为

  1. protected $lists_condition = [];

例如加入企业主键限制

  1. use think\bit\traits\ListsModel;
  2. class AdminClass extends Base {
  3. use ListsModel;
  4. protected $model = 'admin';
  5. protected $lists_condition = [
  6. ['enterprise', '=', 1]
  7. ];
  8. }

如果接口的查询条件较为特殊,可以重写 lists_condition_query

  1. use think\bit\traits\ListsModel;
  2. class AdminClass extends Base {
  3. use ListsModel;
  4. protected $model = 'admin';
  5. public function __construct(App $app = null)
  6. {
  7. parent::__construct($app);
  8. $this->lists_condition_query = function (Query $query) {
  9. $query->whereOr([
  10. 'type' => 1
  11. ]);
  12. };
  13. }
  14. }

如果需要列表按条件排序,只需要重写 lists_orders,默认为

  1. protected $lists_orders = 'create_time desc';

例如按年龄进行排序

  1. use think\bit\traits\ListsModel;
  2. class AdminClass extends Base {
  3. use ListsModel;
  4. protected $model = 'admin';
  5. protected $lists_orders = 'age desc';
  6. }

如需要给接口限制返回字段,只需要重写 lists_field,默认为

  1. protected $lists_field = ['update_time,create_time', true];

例如返回除 update_time 修改时间所有的字段

  1. use think\bit\traits\ListsModel;
  2. class AdminClass extends Base {
  3. use ListsModel;
  4. protected $model = 'admin';
  5. protected $lists_field = ['update_time', true];
  6. }

如自定义返回结果,则需要调用生命周期 ListsCustom

  1. use think\bit\traits\ListsModel;
  2. use think\bit\lifecycle\ListsCustom;
  3. class AdminClass extends Base implements ListsCustom {
  4. use ListsModel;
  5. protected $model = 'admin';
  6. public function __listsCustomReturn(Array $lists, int $total)
  7. {
  8. return [
  9. 'error' => 0,
  10. 'data' => [
  11. 'lists' => $lists,
  12. 'total' => $total,
  13. ]
  14. ];
  15. }
  16. }

__listsCustomReturn 需要返回整体的响应结果

  1. return [
  2. 'error' => 0,
  3. 'data' => [
  4. 'lists' => $lists,
  5. 'total' => $total,
  6. ]
  7. ];
  • data array 原数据

AddModel 新增数据

引入特性,需要定义必须的操作模型 model

  1. use think\bit\traits\AddModel;
  2. class AdminClass extends Base {
  3. use AddModel;
  4. protected $model = 'admin';
  5. }

合并模型验证器下 add 场景,所以需要对应创建验证器场景 validate/AdminClass, 并加入场景 add

  1. use think\Validate;
  2. class AdminClass extends Validate
  3. {
  4. protected $rule = [
  5. 'name' => 'require',
  6. ];
  7. protected $scene = [
  8. 'add' => ['name'],
  9. ];
  10. }

如自定义前置处理,则需要调用生命周期 AddBeforeHooks

  1. use think\bit\traits\AddModel;
  2. use think\bit\lifecycle\AddBeforeHooks;
  3. class AdminClass extends Base implements AddBeforeHooks {
  4. use AddModel;
  5. protected $model = 'admin';
  6. public function __addBeforeHooks()
  7. {
  8. return true;
  9. }
  10. }

__addBeforeHooks 的返回值为 false 则在此结束执行,并返回 add_before_result 属性的值,默认为:

  1. protected $add_before_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:before_fail'
  4. ];

在生命周期函数中可以通过重写自定义前置返回

  1. use think\bit\traits\AddModel;
  2. use think\bit\lifecycle\AddBeforeHooks;
  3. class AdminClass extends Base implements AddBeforeHooks {
  4. use AddModel;
  5. protected $model = 'admin';
  6. public function __addBeforeHooks()
  7. {
  8. $this->add_before_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:only'
  11. ];
  12. return false;
  13. }
  14. }

如自定义后置处理,则需要调用生命周期 AddAfterHooks

  1. use think\bit\traits\AddModel;
  2. use think\bit\lifecycle\AddAfterHooks;
  3. class AdminClass extends Base implements AddAfterHooks {
  4. use AddModel;
  5. protected $model = 'admin';
  6. public function __addAfterHooks($pk)
  7. {
  8. return true;
  9. }
  10. }

pk 为模型写入后返回的主键,__addAfterHooks 的返回值为 false 则在此结束执行进行事务回滚,并返回 add_after_result 属性的值,默认为:

  1. protected $add_after_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:after_fail'
  4. ];

在生命周期函数中可以通过重写自定义后置返回

  1. use think\bit\traits\AddModel;
  2. use think\bit\lifecycle\AddAfterHooks;
  3. class AdminClass extends Base implements AddAfterHooks {
  4. use AddModel;
  5. protected $model = 'admin';
  6. public function __addAfterHooks($pk)
  7. {
  8. $this->add_after_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:redis'
  11. ];
  12. return false;
  13. }
  14. }

EditModel 编辑数据

条件查询:请求可使用 id 或 where 字段进行查询,二者选一即可

  • id int|string
  • where array,必须使用数组方式来定义
  1. $this->post['where'] = [
  2. ['name', '=', 'van']
  3. ];

引入特性,需要定义必须的操作模型 model

  1. use think\bit\traits\EditModel;
  2. class AdminClass extends Base {
  3. use EditModel;
  4. protected $model = 'admin';
  5. }

自定义删除验证器为 edit_validate,默认为

  1. protected $edit_validate = [
  2. 'id' => 'require',
  3. 'switch' => 'bool'
  4. ];

也可以在控制器中针对性修改

  1. use think\bit\traits\EditModel;
  2. class AdminClass extends Base {
  3. use EditModel;
  4. protected $model = 'admin';
  5. protected $edit_validate = [
  6. 'id' => 'require'
  7. 'switch' => 'bool',
  8. 'status' => 'require',
  9. ];
  10. }

合并模型验证器下 edit 场景,所以需要对应创建验证器场景 validate/AdminClass,edit_switch 为 false 下有效, 并加入场景 edit

  1. use think\Validate;
  2. class AdminClass extends Validate
  3. {
  4. protected $rule = [
  5. 'name' => 'require',
  6. ];
  7. protected $scene = [
  8. 'edit' => ['name'],
  9. ];
  10. }

如自定义前置处理,则需要调用生命周期 EditBeforeHooks

  1. use think\bit\traits\EditModel;
  2. use think\bit\lifecycle\EditBeforeHooks;
  3. class AdminClass extends Base implements EditBeforeHooks {
  4. use EditModel;
  5. protected $model = 'admin';
  6. public function __editBeforeHooks()
  7. {
  8. return true;
  9. }
  10. }

__editBeforeHooks 的返回值为 false 则在此结束执行,并返回 edit_before_result 属性的值,默认为:

  1. protected $edit_before_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:before_fail'
  4. ];

在生命周期函数中可以通过重写自定义前置返回

  1. use think\bit\traits\EditModel;
  2. use think\bit\lifecycle\EditBeforeHooks;
  3. class AdminClass extends Base implements EditBeforeHooks {
  4. use EditModel;
  5. protected $model = 'admin';
  6. public function __editBeforeHooks()
  7. {
  8. $this->edit_before_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:only'
  11. ];
  12. return false;
  13. }
  14. }

如自定义后置处理,则需要调用生命周期 EditAfterHooks

  1. use think\bit\traits\EditModel;
  2. use think\bit\lifecycle\EditAfterHooks;
  3. class AdminClass extends Base implements EditAfterHooks {
  4. use EditModel;
  5. protected $model = 'admin';
  6. public function __editAfterHooks()
  7. {
  8. return true;
  9. }
  10. }

__editAfterHooks 的返回值为 false 则在此结束执行进行事务回滚,并返回 edit_after_result 属性的值,默认为:

  1. protected $edit_after_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:after_fail'
  4. ];

在生命周期函数中可以通过重写自定义后置返回

  1. use think\bit\traits\EditModel;
  2. use think\bit\lifecycle\EditAfterHooks;
  3. class AdminClass extends Base implements EditAfterHooks {
  4. use EditModel;
  5. protected $model = 'admin';
  6. public function __editAfterHooks()
  7. {
  8. $this->edit_after_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:redis'
  11. ];
  12. return false;
  13. }
  14. }

DeleteModel 删除数据

条件查询:请求可使用 id 或 where 字段进行查询,二者选一即可

  • id int|string
  • where array,必须使用数组方式来定义
  1. $this->post['where'] = [
  2. ['name', '=', 'van']
  3. ];

引入特性,需要定义必须的操作模型 model

  1. use think\bit\traits\DeleteModel;
  2. class AdminClass extends Base {
  3. use DeleteModel;
  4. protected $model = 'admin';
  5. }

自定义删除验证器为 delete_validate,默认为

  1. protected $delete_validate = [
  2. 'id' => 'require'
  3. ];

也可以在控制器中针对性修改

  1. use think\bit\traits\DeleteModel;
  2. class AdminClass extends Base {
  3. use DeleteModel;
  4. protected $model = 'admin';
  5. protected $delete_validate = [
  6. 'id' => 'require',
  7. 'name' => 'require'
  8. ];
  9. }

如自定义前置处理,则需要调用生命周期 DeleteBeforeHooks

  1. use think\bit\traits\DeleteModel;
  2. use think\bit\lifecycle\DeleteBeforeHooks;
  3. class AdminClass extends Base implements DeleteBeforeHooks {
  4. use DeleteModel;
  5. protected $model = 'admin';
  6. public function __deleteBeforeHooks()
  7. {
  8. return true;
  9. }
  10. }

__deleteBeforeHooks 的返回值为 false 则在此结束执行,并返回 delete_before_result 属性的值,默认为:

  1. protected $delete_before_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:before_fail'
  4. ];

在生命周期函数中可以通过重写自定义前置返回

  1. use think\bit\traits\DeleteModel;
  2. use think\bit\lifecycle\DeleteBeforeHooks;
  3. class AdminClass extends Base implements DeleteBeforeHooks {
  4. use DeleteModel;
  5. protected $model = 'admin';
  6. public function __deleteBeforeHooks()
  7. {
  8. $this->delete_before_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:only'
  11. ];
  12. return false;
  13. }
  14. }

判断是否有存在事务之后模型写入之前的处理,如该周期处理,则需要调用生命周期 DeletePrepHooks

  1. use think\bit\traits\DeleteModel;
  2. use think\bit\lifecycle\DeletePrepHooks;
  3. class AdminClass extends Base implements DeletePrepHooks {
  4. use DeleteModel;
  5. protected $model = 'admin';
  6. public function __deletePrepHooks()
  7. {
  8. return true;
  9. }
  10. }

__deletePrepHooks 的返回值为 false 则在此结束执行进行事务回滚,并返回 delete_prep_result 属性的值,默认为:

  1. protected $delete_prep_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:prep_fail'
  4. ];

在生命周期函数中可以通过重写自定义返回

  1. use think\bit\traits\DeleteModel;
  2. use think\bit\lifecycle\DeletePrepHooks;
  3. class AdminClass extends Base implements DeletePrepHooks {
  4. use DeleteModel;
  5. protected $model = 'admin';
  6. public function __deletePrepHooks()
  7. {
  8. $this->delete_prep_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:insert'
  11. ];
  12. return false;
  13. }
  14. }

如自定义后置处理,则需要调用生命周期 DeleteAfterHooks

  1. use think\bit\traits\DeleteModel;
  2. use think\bit\lifecycle\DeleteAfterHooks;
  3. class AdminClass extends Base implements DeleteAfterHooks {
  4. use DeleteModel;
  5. protected $model = 'admin';
  6. public function __deleteAfterHooks()
  7. {
  8. return true;
  9. }
  10. }

__deleteAfterHooks 的返回值为 false 则在此结束执行进行事务回滚,并返回 delete_after_result 属性的值,默认为:

  1. protected $delete_after_result = [
  2. 'error' => 1,
  3. 'msg' => 'error:after_fail'
  4. ];

在生命周期函数中可以通过重写自定义后置返回

  1. use think\bit\traits\DeleteModel;
  2. use think\bit\lifecycle\DeleteAfterHooks;
  3. class AdminClass extends Base implements DeleteAfterHooks {
  4. use DeleteModel;
  5. protected $model = 'admin';
  6. public function __deleteAfterHooks()
  7. {
  8. $this->delete_after_result = [
  9. 'error'=> 1,
  10. 'msg'=> 'error:redis'
  11. ];
  12. return false;
  13. }
  14. }

lifecycle 生命周期

  • GetBeforeHooks 单条数据的通用请求处理前置自定义周期
    • __getBeforeHooks() 单条数据前置周期
      • return boolean,返回值为 false 则在此结束执行
  • GetCustom 单条数据的通用请求处理自定义返回周期
    • __getCustomReturn($data) 单条数据前置周期
      • data array 原数据
  • ListsBeforeHooks 分页数据的通用请求处理前置自定义周期
    • __listsBeforeHooks() 分页数据前置周期
      • return boolean,返回值为 false 则在此结束执行
  • ListsCustom 分页数据的通用请求处理自定义返回周期
    • __listsCustomReturn(Array $lists, int $total) 分页数据自定义返回周期
      • lists array 原数据
      • total int 数据总数
  • OriginListsBeforeHooks 列表数据请求前置处理周期
    • __originListsBeforeHooks() 列表数据前置周期
      • return boolean,返回值为 false 则在此结束执行
  • OriginListsCustom 列表数据的通用请求处理自定义返回周期
    • __originListsCustomReturn(Array $lists) 列表数据自定义返回周期
      • lists array 原数据
  • AddBeforeHooks 新增数据的通用请求处理前置自定义周期
    • __addBeforeHooks() 新增前置周期
      • return boolean,返回值为 false 则在此结束执行
  • AddAfterHooks 新增数据的通用请求处理后置自定义周期
    • __addAfterHooks($pk) 新增后置周期
      • pk string|int 模型写入后返回的主键
      • return boolean,返回值为 false 则在此结束执行进行事务回滚
  • EditBeforeHooks 编辑数据的通用请求处理前置自定义周期
    • __editBeforeHooks() 编辑前置周期
      • return boolean,返回值为 false 则在此结束执行
  • EditAfterHooks 编辑数据的通用请求处理后置自定义周期
    • __editBeforeHooks() 编辑前置周期
      • return boolean,返回值为 false 则在此结束执行进行事务回滚
  • DeleteBeforeHooks 删除数据的通用请求处理前置自定义周期
    • __deleteBeforeHooks() 删除前置周期
      • return boolean,返回值为 false 则在此结束执行
  • DeletePrepHooks 删除数据的通用请求处理在事务之后模型写入之前的的自定义周期
    • __deletePrepHooks() 删除在事务之后模型写入之前的周期
      • return boolean,返回值为 false 则在此结束执行进行事务回滚
  • DeleteAfterHooks 删除数据的通用请求处理后置自定义周期
    • __deleteAfterHooks() 删除后置周期
      • return boolean,返回值为 false 则在此结束执行进行事务回滚