You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Deepak Nigam (JIRA)" <ji...@apache.org> on 2018/09/24 12:50:00 UTC

[jira] [Commented] (OFBIZ-10586) Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'

    [ https://issues.apache.org/jira/browse/OFBIZ-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625770#comment-16625770 ] 

Deepak Nigam commented on OFBIZ-10586:
--------------------------------------

Uploaded the patch for the fix. Related data correction is available in OFBiz-10574.[OFBiz-10574|https://issues.apache.org/jira/browse/OFBIZ-10574]

> Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-10586
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10586
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: securityext
>    Affects Versions: Trunk
>            Reporter: Deepak Nigam
>            Assignee: Deepak Nigam
>            Priority: Major
>         Attachments: OFBiz-10586.patch
>
>
> In the definition of 'SecurityGroupPermission' entity, the relation type with 'SecurityPermission' entity is 'one-nofk'. Hence the system is allowing to use the permissions not defined anywhere. (ex. ORDERMGR_CRQ_ADMIN/ORDERMGR_CRQ_UPDATE, ASSETMAINT_VIEW).
>  
> Change the relation type to 'one' to maintain the referential integrity.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)