db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1539) As per the functional spec attached to DERBY-1330, a trigger should be dropped when a privilege required by the trigger is revoked.
Date Tue, 01 Aug 2006 03:44:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1539?page=comments#action_12424724 ] 
            
Daniel John Debrunner commented on DERBY-1539:
----------------------------------------------

I'm wondering if one could see the invalidation due to a revoke in a different light, more
of a invalidation followed by a re-validate. Thus rather than having to carry around extra
information about what exactly has changed, just have the trigger (dependent) receive notification
that its privileges  have changed in some way and now it needs to re-validate and check all
of its permissions. Thus which privilege has dropped  is no that important, just that fact
that re-validation is required.

I think a step like this is needed anyway if an object was dependent on a privilege granted
to an individual that existed at create time but subsequently could be statisfied by the same
privilege granted to PUBLIC.

I assume that trigger re-compilation like this must work, say a trigger's action statement
is defined as an INSERT, then that statement must need to be recompiled if an index is added
or dropped from the table. Or with the various trigger re-compile bugs recently is trigger
re-compilation not implemented at all?


> 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

        

Mime
View raw message