[DERBY-2594] Revoking a privilege from an SQL Object should invalidate statements dependent on that object

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.3.1.4
• Component/s: SQL
• Urgency: Normal
• Assignee: Dyre Tjeldvoll
• Reporter: Dyre Tjeldvoll
• Created: 26/Apr/07 11:35
• Updated: 08/Jul/08 13:23
• Resolved: 21/May/07 10:42

Description

Revoking a privilege on a table will currently cause the DependencyManager.invalidateFor() to be called on the table's TablePermsDescriptor with the action=REVOKE_PRIVILEGE. However, the prepared statements that refer to that table are dependents of the table's TableDescriptor, but NOT its TablePermsDescriptor, so the statements are not invalidated after revoke.

This problem is currently hidden by the fact that authorization is checked on every execution, but this will change when language result sets are no longer reused (see DERBY-827).

Issue Links

• is related to: DERBY-827 Performance can be improved by re-using language ResultSets across Activation executions.
• relates to: DERBY-3736 Revoking a column level privilege from a user, a prepared statement relying on that privilege can still be executed
• relates to: DERBY-827 Performance can be improved by re-using language ResultSets across Activation executions.