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-3877) SQL roles: build support for dblook
Date Mon, 15 Sep 2008 02:17:46 GMT

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

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

      Component/s: Tools
      Description: 
dblook does have support for grant/revoke although I umsure if its quality, cf, my questions
in DERBY-3868. Nevertheless, I choose to build support for roles for dblook.
Since role creation and granting of roles is only allowed for the data base owner in the first
basic
roles implementation, expending the existing dblook tests to just dump the roles and roles
grants should be easy.

In general though, the dblook output file, i order to receate a database, must potentially
use several connections 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.

My intention with this issue is just to add support for dumping roles and role grants.
    Fix Version/s: 10.5.0.0

> 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
>
>
> dblook does have support for grant/revoke although I umsure if its quality, cf, my questions
> in DERBY-3868. Nevertheless, I choose to build support for roles for dblook.
> Since role creation and granting of roles is only allowed for the data base owner in
the first basic
> roles implementation, expending the existing dblook tests to just dump the roles and
roles grants should be easy.
> In general though, the dblook output file, i order to receate a database, must potentially
use several connections 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.
> 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.


Mime
View raw message