db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3666) Make role descriptor a dependency Provider
Date Thu, 15 May 2008 11:53:55 GMT

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

Dag H. Wanvik commented on DERBY-3666:

Thanks for reviewing this patch, Rick!

a) RoleDescriptor.getObjectName: I agree.

b) RoleDescriptor vs. RoleGrantDescriptor : I agree this can be a bit
confusing.  SQL models a role creation as a grant, too (grantor:
_SYSTEM), which is reflected in the implementation.  In some contexts,
especially if we later want to implement the full standard for roles
(non-dbo can define a role, WITH ADMIN option, grantor specification),
it will be useful to view the descriptor as a grant, other times as
the role definition. But in any case, since all SYSROLES rows are
representable with the current RoleDescriptor, RoleGrantDescriptor
would just as suitable as a name. Let me think about this one; right
now I favor your suggestion.

> Make role descriptor a dependency Provider
> ------------------------------------------
>                 Key: DERBY-3666
>                 URL: https://issues.apache.org/jira/browse/DERBY-3666
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Security, SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>         Attachments: derby-3666-1.diff, derby-3666-1.stat
> Since dropping roles and revoking role grants (and setting the current
> role) can effect dependent objects, we need to track such
> dependencies. Derby already has a system for this, so we make the role
> descriptor as Provider in that system. This allows us to track
> dependencies that view, constraints and triggers, as well
> prepared statements and/or activations, may have on roles.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message