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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/09/30 04:08:07 UTC

[jira] [Updated] (DERBY-3928) SQL roles: Enable the use of StatementRolePermission

     [ https://issues.apache.org/jira/browse/DERBY-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-3928:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
    
> SQL roles: Enable the use of StatementRolePermission
> ----------------------------------------------------
>
>                 Key: DERBY-3928
>                 URL: https://issues.apache.org/jira/browse/DERBY-3928
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Dag H. Wanvik
>              Labels: derby_triage10_10
>
> A privilege to CREATE and DROP roles (StatementRolePermission) was
> added as part of the initial roles implementation. 
> The permission was added to prepare for future need to grant this
> privilege. However, it is not being used for checking whether
> CREATE/DROP role is allowed yet. The current code just tests if the
> executing session is the database owner instead of checking that the
> session has the role create/drop privilege).
> Making use of the permission would not yield any new functionality,
> but would prepare the way for delegating this privilege to other
> users. Furthermore, there is as yet no syntax for granting or revoking
> this privilege (only the database owner is supposed to enjoy it for
> now).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira