[
https://issues.apache.org/jira/browse/DERBY-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621931#action_12621931
]
Rick Hillegas commented on DERBY-3743:
--------------------------------------
Hi Dag,
The patch looks good to me. You might want to adjust the header comment on
DDLConstantAction.storeConstraintDependenciesOnPrivileges(). Right now the
header says " where as constraints only depend on REFERENCES privilege on a
table". That statement used to be true, but with your patch that statement is
no longer true for CHECK constraints.
> Revoking EXECUTE privilege on a function if used in a CHECK constraint:
> implementation problem
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-3743
> URL: https://issues.apache.org/jira/browse/DERBY-3743
> Project: Derby
> Issue Type: Improvement
> Components: Security, SQL
> Affects Versions: 10.5.0.0
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Fix For: 10.5.0.0
>
> Attachments: derby-3743-show-constraint-invalidate-actions.diff,
> derby-3743-show-constraint-invalidate-actions.stat, derby-3743.diff,
> derby-3743.stat, derby-3743b-1.diff, derby-3743b-1.stat
>
>
> The docs say that REVOKE EXECUTE ... RESTRICT should
> fail if there is a dependent constraint:
> "The RESTRICT clause specifies that the EXECUTE privilege cannot be
> revoked if the specified routine is used in a view, trigger, or
> constraint, and the privilege is being revoked from the owner of the
> view, trigger, or constraint."
> Revoking the privilege will be correctly restricted, but possibly for the
> wrong reason.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
