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

2018-11-23 Thread Deepak Nigam (JIRA)


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

Deepak Nigam commented on OFBIZ-10586:
--

As discussed, there is nothing to do further in this ticket so closing it.

> 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: Suraj Khurana
>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)


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

2018-11-23 Thread Jacques Le Roux (JIRA)


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

Jacques Le Roux commented on OFBIZ-10586:
-

I think this should be closed as "Won't Do" following the discussion, notably 
[~deepak.dixit]'s advice:
{quote}It looks good to have one FK relationship while reviewing entity def 
found following description. This is by design before proceeding we need to 
check this.

"Defines a permission available to a security group; there is no FK to 
SecurityPermission because we want to leave open the possibility of ad-hoc 
permissions, especially for the Entity Data Maintenance pages which have TONS 
of permissions"

Thanks & Regards
-- Deepak Dixit
{quote}

> 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: Suraj Khurana
>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)


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

2018-09-24 Thread Deepak Nigam (JIRA)


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

Deepak Nigam commented on OFBIZ-10586:
--

Here is the [link|https://markmail.org/message/wshrwsr6pdy474yw] of related 
discussion in the dev mailing list.

> 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)


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

2018-09-24 Thread Deepak Nigam (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)