[ http://issues.apache.org/jira/browse/DERBY-1581?page=comments#action_12423396 ] Mamta A. Satoor commented on DERBY-1581: ----------------------------------------
I tried Dan's draft patch with my trigger revoke changes and the grant revoke test and derbyall ran fine. In my particular case, I have veritifed that Dependency manager is not recreating the provider object (PermissionDescriptor) because if it was, there would have been a null ptr exception. So, I will give a go ahead to Dan's patch from the grant/revoke point of view. I will go ahead and submit my changes for grant/revoke work as part of DERBY-1539 but that patch should be submitted only after the draft patch attached to this Jira entry is committed. > BasicDependencyManager re-loads the Provider multiple times from the > DataDictionary when loading the stored dependencies for the Provider. > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-1581 > URL: http://issues.apache.org/jira/browse/DERBY-1581 > Project: Derby > Issue Type: Improvement > Components: SQL > Reporter: Daniel John Debrunner > Assigned To: Daniel John Debrunner > Priority: Minor > Fix For: 10.2.0.0 > > Attachments: derby1581_draft.txt > > > From work on DERBY-1593 & DERBY-1330 it was discovered the > DependencyMangerImpl loaded the same Provier multiple times from the > DataDictionary while loading the stored dependecies and converting them to an > in-memory form. There is no need to load the Provider from the > DataDictionary because it is passed into the DependencyManger.invalidateFor > call that results in the loading of the stored dependencies. -- 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
