Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <25594931.112521286975553618.JavaMail.jira@thor>
Date: Wed, 13 Oct 2010 09:12:33 -0400 (EDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-4844) Implement DROP SCHEMA CASCADE
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Implement DROP SCHEMA CASCADE
-----------------------------

                 Key: DERBY-4844
                 URL: https://issues.apache.org/jira/browse/DERBY-4844
             Project: Derby
          Issue Type: Improvement
          Components: SQL
            Reporter: Rick Hillegas


Right now you can only drop an empty schema. This is the command you use:

   DROP SCHEMA schemaName RESTRICT

Before dropping a schema, you need to drop all of its objects in the reverse order that you created them. That prevents you from tripping across dependencies among the objects (like constraints). There appears to be some interest in implementing the standard CASCADE clause:

  DROP SCHEMA schemaName CASCADE

This version of the DROP SCHEMA command would figure out the correct order in which to drop the objects inside the schema. The command could still fail, of course, if other schemas depended on objects in the dropped schema.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.