[
https://issues.apache.org/jira/browse/DERBY-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272781#comment-13272781
]
Dag H. Wanvik commented on DERBY-5747:
--------------------------------------
Rick, we probably should use SYSUSERS to vet new roles as well to avoid
collisions: roles names and user names are in the same SQL namespace. Other
future possiblities include
usage statistics, foreign key for action trail logging ("who changed this?"),
password history.
> 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
