Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <21338998.1159931120069.JavaMail.root@brutus>
Date: Tue, 3 Oct 2006 20:05:20 -0700 (PDT)
From: "Bryan Pendleton (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-1926) Provide documentation for ALTER TABLE
 DROP COLUMN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Provide documentation for ALTER TABLE DROP COLUMN
-------------------------------------------------

                 Key: DERBY-1926
                 URL: http://issues.apache.org/jira/browse/DERBY-1926
             Project: Derby
          Issue Type: New Feature
          Components: Documentation
    Affects Versions: 10.3.0.0
            Reporter: Bryan Pendleton
            Priority: Minor


The documentation will need to be updated after DERBY-1489 is committed. The reference manual will need to describe how to use the new ALTER TABLE DROP COLUMN feature to drop a column from a table.

The documentation for the ALTER TABLE command is becoming somewhat unwieldy, so perhaps there is a way to restructure the page to make it easier and more approachable.

In the documentation, it will be important to clearly describe the RESTRICT and CASCADE behaviors, as users may be confused by what things cause RESTRICT to refuse to drop a column. The comments in AlterTableConstantAction.java may help.

Specifically, the documentation should note these possibly unexpected behaviors:
 - If a column is present in one or more indexes, these indexes by themselves do not cause
   RESTRICT to refuse to drop a column. Instead, the column will simply be dropped from
   the index, and if that was the last column in that index, the entire index will be dropped.
 - Explicitly named CHECK constraints will cause RESTRICT to refuse to drop a column, as
   will PRIMARY KEY, FOREIGN KEY, and UNIQUE constrants. However, an unnamed simple
   NOT NULL constraint on a column will NOT cause RESTRICT to refuse to drop it.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira