[DERBY-5747] Native user authentication: Docs do not describe what happens to schema and its SQL objects on SYSCS_UTIL.SYSCS_DROP_USER call

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.9.1.0
• Component/s: Documentation, Services
• Assignee: Camilla Haase
• Reporter: Dag H. Wanvik
• Created: 07/May/12 12:35
• Updated: 21/May/12 15:45
• Resolved: 15/May/12 20:18

Description

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.

Issue Links

• relates to: DERBY-866 Derby User Management Enhancements