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] Updated: (DERBY-3666) Make role descriptor a dependency Provider
Date Fri, 23 May 2008 21:51:56 GMT

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

Dag H. Wanvik updated DERBY-3666:
---------------------------------

    Attachment: derby-3666-2.stat
                derby-3666-2.diff

Uploading derby-3666-2. It is the same as version 1, except I have changed the text of RoleDescriptor.getObjectName
to only use the appropriate SQL keywords (in caps), so that way there should not be a localization
issue for the inlined strings.

> 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, derby-3666-2.diff, derby-3666-2.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.


Mime
View raw message