[
https://issues.apache.org/jira/browse/DERBY-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860254#comment-13860254
]
Rick Hillegas commented on DERBY-6434:
--------------------------------------
The discussion on DERBY-6429 concluded that constraints, generated columns, and
triggers do not impose any privilege burdens on INSERT/UPDATE/DELETE/MERGE
statements. The privilege burdens related to constraints, generated columns,
and triggers are satisfied at DDL time.
As a result, I would state the privilege requirements for INSERT statements as
follows. Let P be the union of the privileges granted to the current user and
the privileges granted to the current role.
1) P must contain INSERT privilege for the target table.
2) P must contain all privileges needed to evaluate the query expression in the
INSERT statement. These privileges include:
a) SELECT privilege on all columns mentioned in the query expression.
b) EXECUTE privilege on all functions mentioned in the query expression.
c) USAGE privilege on all types, sequences, and aggregates mentioned in the
query expression.
> Incorrect privileges may be required for INSERT and DELETE statements.
> ----------------------------------------------------------------------
>
> Key: DERBY-6434
> URL: https://issues.apache.org/jira/browse/DERBY-6434
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.11.0.0
> Reporter: Rick Hillegas
>
> This issue is a place to address problems with INSERT and DELETE statements
> similar to the problems affecting UPDATE statements recorded on DERBY-6429.
> In particular, DERBY-6432 and DERBY-6433 list some of the problems with
> INSERT statements.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
