[ 
http://issues.apache.org/jira/browse/DERBY-1539?page=comments#action_12424737 ] 
            
Mamta A. Satoor commented on DERBY-1539:
----------------------------------------

Another solution I am thinking is have the ViewDescriptor, ConstraintDescriptor 
and TriggerDescriptor keep the information about what privileges they require. 
This can be done when these objects get loaded from the data dictionary. Then 
when they get the specific revoke actions like what my patch sends, the 
dependent objects will check their privilege requirement against what is being 
revoked in the PermissionDescriptor and then drop themselves if their required 
privilege is being revoked. So, rather than contaminate the dependency manager 
code with special cases, have the dependent descriptors aware of their 
privilege requirements. This seems to sound more logical. This will not solve 
the problem of having the dependent object depend on the next available 
privilege when one of it's current privilege is revoked but may be it can be 
tackled later.

Let me know if anyone has any opinion about this approach. Otherwise, I am 
thinking I am going to start looking at this approach.

> As per the functional spec attached to DERBY-1330, a trigger should be 
> dropped when a privilege required by the trigger is revoked.
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1539
>                 URL: http://issues.apache.org/jira/browse/DERBY-1539
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.2.0.0
>            Reporter: Mamta A. Satoor
>         Assigned To: Mamta A. Satoor
>             Fix For: 10.2.0.0
>
>         Attachments: DERBY1539V1hashCodeEqualsDiff.txt, 
> DERBY1539V1hashCodeEqualsStat.txt, DERBY1539V2diffDropTriggerOnRevoke.txt, 
> DERBY1539V2statDropTriggerOnRevoke.txt, 
> DERBY1539V3diffDropTriggerOnRevoke.txt, 
> DERBY1539V3statDropTriggerOnRevoke.txt, 
> DERBY1539V4diffDropTriggerOnRevoke.txt, 
> DERBY1539V4diffDropTriggerOnRevokeRequiredPrivilege.txt, 
> DERBY1539V4statDropTriggerOnRevokeRequiredPrivilege.txt
>
>
> A trigger tracks its privileges requirements using Derby's Dependency 
> Manager. If any one of those required privileges are revoked, the trigger 
> should be dropped automatically. 
> I am just creating a new jira entry here so it is easier to track sub items 
> of DERBY-1330. Will link this Jira entry to DERBY-1330.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to