Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 11 May 2012 14:58:52 +0000 (UTC)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1727814771.54670.1336748332334.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1672556442.34059.1336394211309.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5747) Native user authentication: Docs do
 not describe what happens to schema and its SQL objects on
 SYSCS_UTIL.SYSCS_DROP_USER call
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase updated DERBY-5747:
-----------------------------

    Attachment: rrefnativedropuserproc.html
                DERBY-5747.diff

Attaching DERBY-5747.diff and rrefnativedropuserproc.html, which adds a new paragraph to the topic on SYSCS_UTIL.SYSCS_DROP_USER:

M       src/ref/rrefnativedropuserproc.dita

Thanks in advance for comments!
                
> 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