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] [Created] (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 Mon, 07 May 2012 12:36:51 GMT
Dag H. Wanvik created DERBY-5747:
------------------------------------

             Summary: 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


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