[ http://issues.apache.org/jira/browse/DERBY-1539?page=comments#action_12424676 ]
Daniel John Debrunner commented on DERBY-1539:
----------------------------------------------
I'm looking at this patch and need to study it more, but I think having the dependency manager
take specific actions based upon the type of provider or dependent is not a good approach.
I know the code does this already for TableDescriptors (at least) and it's fair you copied
that approach, but I'd like to think about if it can be avoided.
> 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
|