[
https://issues.apache.org/jira/browse/DERBY-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik closed DERBY-3877.
--------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed patch derby-3877-2 as 700295, closing.
> SQL roles: build support for dblook
> -----------------------------------
>
> Key: DERBY-3877
> URL: https://issues.apache.org/jira/browse/DERBY-3877
> Project: Derby
> Issue Type: Sub-task
> Components: Tools
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Fix For: 10.5.0.0
>
> Attachments: derby-3877-1.diff, derby-3877-1.stat, derby-3877-2.diff,
> derby-3877-2.stat
>
>
> dblook does have support for grant/revoke although I am unsure of its
> quality, cf, my questions
> in DERBY-3868. Nevertheless, I choose to build support for roles for dblook.
> Since role creation and the granting of roles is only allowed for the data
> base owner in the first basic
> roles implementation, expanding the existing dblook tests to just dump the
> roles and roles grants should be easy.
> In general though, the dblook output file, in order to receate a database,
> must potentially use several connection, so the objects will be owned by the
> original owner. [The model for running the presently generated script run
> seems to be within one connection.] Setting roles properly to be able to
> recreate a view with the correct owner, for example, would be part of such a
> more advanced script which would be object owner aware.
> My intention with this issue is just to add support for dumping roles and
> role grants.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
