[DERBY-1643] A "revoke execute ... restrict" should fail if there are dependent objects on the execute privilege

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: SQL
• Assignee: Mamta A. Satoor
• Reporter: Mamta A. Satoor
• Created: 04/Aug/06 02:51
• Updated: 01/Jul/09 00:34
• Resolved: 30/Aug/06 06:29

Description

As per the functional spec attached to DERBY-1330, a "revoke execute ... restrict" should fail if there are dependent objects on the execute privilege

In order to implement this, when revoke execute is executed, a special invalidation action should be sent and dependent objects will need to catch that invalidation and throw an exception. If there are no dependents, then no exception will be thrown and revoke execute will succeed.

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.

See the functional spec attached to DERBY-1330

Issue Links

• is duplicated by: DERBY-1642 As per the functional spec attached to DERBY-1330, a "revoke execute ... restrict" should fail if there are dependent objects on the execute privilege
• is part of: DERBY-1330 Provide runtime privilege checking for grant/revoke functionality
• relates to: DERBY-1632 During revoke privilege, Derby does not look for replacement privilege for the dependent objects and simply drops the dependent objects. This is not SQL compliant and should be fixed.