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-5747) Native user authentication: Docs do not describe what happens to schema and its SQL objects on SYSCS_UTIL.SYSCS_DROP_USER call
Date Fri, 11 May 2012 22:15:50 GMT

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

Dag H. Wanvik commented on DERBY-5747:
--------------------------------------

Thanks, Kim. Looks right to me; it reflects the current implementation, I think. +1 from me,
but I hope Rick can also vet this.

                
> 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: DERBY-5747.diff, repro2.sh, rrefnativedropuserproc.html
>
>
> 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