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 Sat, 22 Jul 2006 18:49:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1539?page=comments#action_12422842 ] 
            
Daniel John Debrunner commented on DERBY-1539:
----------------------------------------------

Mamta, I understand  your general comments about the dependency manager and not knowing the
tableUUID etc, but it doesn't clear up my confusion.
I'm trying to understand  how executing a REVOKE statement like:

 REVOKE SELECT ON TABLE S1.T1 FROM dan

relates to what you wrote initially:

"But for revoke functionality, dependency manager is going to keep various object dependencies
on PermissionsDescriptor using the UUID attached to the PermissionsDescriptor. Hence, when
dependency manager works with PermissionsDescriptor, it only knows about UUID and doesn't
know anything about tableUUID/routineUUID and hashCode & equals method need to be able
to handle that." 

Maybe my question is, at what point in time during the execution of a REVOKE do you end up
with a PermissionsDescriptor  that only has been populated with its object UUID, and what
permission does the PermissionsDescriptor  represent?

I think I'm still a little in the dark as to the overall  problem this patch is addressing,
rather than the specific of a cache lookup not working.






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