Laravel Spatie权限-未找到基表或视图:1146表'my_database.models'不存在

时间:2020-05-02 05:03:50

标签: php mysql laravel spatie laravel-permission

使用Spatie权限并尝试使用以下角色分配角色时出现错误:

$user->assignRole('admin');

错误如下:

Base table or view not found: 1146 Table 'my_database.models' doesn't exist (SQL: select * from `models` where `user_id` = 38 and `model_type` = App\User) 

在哪里设置了“模型”值,该表不存在,但是,在哪里设置值?我似乎找不到它,我已经在config/permission.php内部进行了检查。

我的permission文件如下:

return [

'models' => [

    /*
     * When using the "HasPermissions" trait from this package, we need to know which
     * Eloquent model should be used to retrieve your permissions. Of course, it
     * is often just the "Permission" model but you may use whatever you like.
     *
     * The model you want to use as a Permission model needs to implement the
     * `Spatie\Permission\Contracts\Permission` contract.
     */

    'permission' => Spatie\Permission\Models\Permission::class,

    /*
     * When using the "HasRoles" trait from this package, we need to know which
     * Eloquent model should be used to retrieve your roles. Of course, it
     * is often just the "Role" model but you may use whatever you like.
     *
     * The model you want to use as a Role model needs to implement the
     * `Spatie\Permission\Contracts\Role` contract.
     */

    'role' => Spatie\Permission\Models\Role::class,

],

'table_names' => [

    /*
     * When using the "HasRoles" trait from this package, we need to know which
     * table should be used to retrieve your roles. We have chosen a basic
     * default value but you may easily change it to any table you like.
     */

    'roles' => 'roles',

    /*
     * When using the "HasPermissions" trait from this package, we need to know which
     * table should be used to retrieve your permissions. We have chosen a basic
     * default value but you may easily change it to any table you like.
     */

    'permissions' => 'permissions',

    /*
     * When using the "HasPermissions" trait from this package, we need to know which
     * table should be used to retrieve your models permissions. We have chosen a
     * basic default value but you may easily change it to any table you like.
     */

    'users_has_permissions' => 'users_has_permissions',

    /*
     * When using the "HasRoles" trait from this package, we need to know which
     * table should be used to retrieve your models roles. We have chosen a
     * basic default value but you may easily change it to any table you like.
     */

    'users_has_roles' => 'users_has_roles',

    /*
     * When using the "HasRoles" trait from this package, we need to know which
     * table should be used to retrieve your roles permissions. We have chosen a
     * basic default value but you may easily change it to any table you like.
     */

    'role_has_permissions' => 'role_has_permissions',
],

'column_names' => [

    /*
     * Change this if you want to name the related model primary key other than
     * `model_id`.
     *
     * For example, this would be nice if your primary keys are all UUIDs. In
     * that case, name this `model_uuid`.
     */

    'model_morph_key' => 'user_id',
],

/*
 * When set to true, the required permission/role names are added to the exception
 * message. This could be considered an information leak in some contexts, so
 * the default setting is false here for optimum safety.
 */

'display_permission_in_exception' => false,

/*
 * By default wildcard permission lookups are disabled.
 */

'enable_wildcard_permission' => false,

'cache' => [

    /*
     * By default all permissions are cached for 24 hours to speed up performance.
     * When permissions or roles are updated the cache is flushed automatically.
     */

    'expiration_time' => \DateInterval::createFromDateString('24 hours'),

    /*
     * The cache key used to store all permissions.
     */

    'key' => 'spatie.permission.cache',

    /*
     * When checking for a permission against a model by passing a Permission
     * instance to the check, this key determines what attribute on the
     * Permissions model is used to cache against.
     *
     * Ideally, this should match your preferred way of checking permissions, eg:
     * `$user->can('view-posts')` would be 'name'.
     */

    'model_key' => 'name',

    /*
     * You may optionally indicate a specific cache driver to use for permission and
     * role caching using any of the `store` drivers listed in the cache.php config
     * file. Using 'default' here means to use the `default` set in cache.php.
     */

    'store' => 'default',
],
];

如您所见,我的数据透视表已设置为:users_has_permissionsusers_has_roles

1 个答案:

答案 0 :(得分:2)

我已经解决了问题,显然您无法更改config/permission.php文件中的键名,所以我有了:

/*
         * When using the "HasPermissions" trait from this package, we need to know which
         * table should be used to retrieve your models permissions. We have chosen a
         * basic default value but you may easily change it to any table you like.
         */

        'user_has_permissions' => 'user_has_permissions',

        /*
         * When using the "HasRoles" trait from this package, we need to know which
         * table should be used to retrieve your models roles. We have chosen a
         * basic default value but you may easily change it to any table you like.
         */

        'user_has_roles' => 'user_has_roles',

我只是将数组中的键设置为开始时的值:

/*
         * When using the "HasPermissions" trait from this package, we need to know which
         * table should be used to retrieve your models permissions. We have chosen a
         * basic default value but you may easily change it to any table you like.
         */

    'model_has_permissions' => 'user_has_permissions',

    /*
     * When using the "HasRoles" trait from this package, we need to know which
     * table should be used to retrieve your models roles. We have chosen a
     * basic default value but you may easily change it to any table you like.
     */

    'model_has_roles' => 'user_has_roles',
相关问题