db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5747) Native user authentication: Docs do not describe what happens to schema and its SQL objects on SYSCS_UTIL.SYSCS_DROP_USER call
Date Tue, 08 May 2012 15:41:49 GMT

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

Rick Hillegas commented on DERBY-5747:
--------------------------------------

Thanks, Dag. Can you list other uses of SYSUSERS which you think we may want to explore in
the future (probably not in 10.9)? This may help us understand whether there are some cheap
changes which we can make in 10.9 in order to support those later extensions. Thanks.
                
> Native user authentication: Docs do not describe what happens to schema and its SQL objects
on SYSCS_UTIL.SYSCS_DROP_USER call
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5747
>                 URL: https://issues.apache.org/jira/browse/DERBY-5747
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation, Services
>    Affects Versions: 10.9.0.0
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>         Attachments: repro2.sh
>
>
> Currently, the schema and the objects remain after the user is dropped, cf. repro2.sh
attached.
> The authorization id of the schema of the dropped user is still that id (dangling) after
DROP.
> Perhaps ownership should revert to the DBO when a user is dropped, or should DROP USER
do a cascade delete?
> There is no way currently to change the ownership of the schema to another user.
> At the very least we should document what happens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message