权限管理_CPS_FUNC_PERMISSION_DATA 2

来源:互联网 发布:淘宝店铺售假多久恢复 编辑:程序博客网 时间:2024/06/06 19:33

<ChineseComment>
数据权限类型ID,来自CPS_DATA_PERMISSION_DEF
</ChineseComment>';

comment on column CPSSYS.CPS_FUNC_PERMISSION_DATA.PARENT_DATAPERMISSION_ID is
'<EnglishName>
Parent Data Permission ID
</EnglishName>

<EnglishComment>
The parent granularity of a data granularity. If the values is null, it means there is no parent granularity.

</EnglishComment>

<ChineseComment>
数据权限类型的父ID,来自CPS_DATA_PERMISSION_DEF。为空表示没有父ID。
</ChineseComment>';

comment on column CPSSYS.CPS_FUNC_PERMISSION_DATA.ALLOWALLITEM is
'<EnglishName>
Allow All Item
</EnglishName>

<EnglishComment>
Indicates whether all data of a granularity can be assigned to a role.
0: Not support.
1: Support
For example, if the current granularity is Reason Type and the value of this filed is set as ''1'',
that means when assigning permissions to a specific role, all reason types can be assigned to the role.
Event if a new reason type is created after the assignment, the role can access the new reason type without assignment again.

</EnglishComment>

<ChineseComment>
是否支持所有取值的授权。例如对REASON_TYPE的授权,如果这里设置为1,那么在操作员做数据权限授权时,
可以直接选择对角色授权REASON_TYPE的所有取值,不需要选择具体哪些取值。
这样即使今后新增了REASON_TYPE,也无需重新对这个角色做授权了。
0-不支持
1-支持
</ChineseComment>';

comment on column CPSSYS.CPS_FUNC_PERMISSION_DATA.IDENTITY_TYPE is
'<EnglishName>
Identity Type
</EnglishName>

<EnglishComment>
Indicates the operator type who can access this granularity.
2000: SP Operator
3000: Organization Operator

</EnglishComment>

<ChineseComment>
数据权限使用的操作员类型
2000: SP操作员
3000: 组织操作员
</ChineseComment>';

alter table CPSSYS.CPS_FUNC_PERMISSION_DATA
   add constraint FK_CPS_FUNC_FK_CPS_FU_CPS_PERM foreign key (PERMISSION_IDENTIFIES)
      references CPSSYS.CPS_PERMISSION_DEF (PERMISSION_IDENTIFIES)
      on update restrict
      on delete restrict;

alter table CPSSYS.CPS_FUNC_PERMISSION_DATA
   add constraint FK_CPS_FUNC_FK_CPS_FU_CPS_DATA foreign key (DATAPERMISSION_ID)
      references CPSSYS.CPS_DATA_PERMISSION_DEF (DATAPERMISSION_ID)
      on update restrict
      on delete restrict;

0 0