You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2014/05/12 15:04:14 UTC

[jira] [Commented] (DERBY-6574) Add privileges checking to SET CONSTRAINTS

    [ https://issues.apache.org/jira/browse/DERBY-6574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995052#comment-13995052 ] 

Dag H. Wanvik commented on DERBY-6574:
--------------------------------------

It seems there are no specific access rules for SET CONSTRAINTS in standard. The deferral only affects the current transaction anyway. So, if a user has privileges to access the tables owning the constraints in question,
the user can also set those constraints' modes.


> Add privileges checking to SET CONSTRAINTS
> ------------------------------------------
>
>                 Key: DERBY-6574
>                 URL: https://issues.apache.org/jira/browse/DERBY-6574
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Dag H. Wanvik
>             Fix For: 10.11.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)