[ https://issues.apache.org/jira/browse/DERBY-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274626#comment-13274626
]
Rick Hillegas commented on DERBY-5747:
--------------------------------------
Thanks Kim. These changes look good to me. +1
> 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
|