[ http://issues.apache.org/jira/browse/DERBY-1539?page=comments#action_12422815 ] Mamta A. Satoor commented on DERBY-1539: ----------------------------------------
While looking at DataDictionaryImpl for something else, I found that there are very few descriptor types that get cached (looks like TableDescriptor and SPSDescriptor and PermissionsDescriptor are the only ones). For all the rest of the descriptors, we always goto system tables. For TableDescriptor and SPSDescriptor, DataDictionary getter methods check to see if Derby is in compile mode and the descriptors are fetched from the cache only if Derby is in compile mode. If not in compile mode, Derby goes to system tables to get TableDescriptor and SPSDescriptor. I am not sure why caching is not used in execute mode for these 2 descriptors, but if we followed the same logic for PermissionDescriptors as well, we will not have the hash key code problem with PermissionDescriptors during the revoke privilege execute phase. Does anyone have any opinion about this? If so, please let me know in next couple days. If not, I will go ahead and mimic the cache bypassing behavior for PermissionDescriptors. > 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
