db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1489) Provide ALTER TABLE DROP COLUMN functionality
Date Tue, 01 Aug 2006 13:43:15 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1489?page=comments#action_12424863 ] 
Rick Hillegas commented on DERBY-1489:

Hi Bryan: Thanks for this great feature. The parser changes look good: thanks for cleaning
up the LOOKAHEADs in alterTableAction().

1) I agree that it would be good to see some tests verifying that privilege descriptors are
cleaned up.

2) I'm curious about why ALTER TABLE DROP COLUMN CASCADE fails if a view mentions the column.
From your comment in altertable.sql, it seems that this puzzles you too. It does look wrong
to me.

> Provide ALTER TABLE DROP COLUMN functionality
> ---------------------------------------------
>                 Key: DERBY-1489
>                 URL: http://issues.apache.org/jira/browse/DERBY-1489
>             Project: Derby
>          Issue Type: New Feature
>          Components: Documentation, SQL
>    Affects Versions:,,,,,,
>            Reporter: Bryan Pendleton
>         Assigned To: Bryan Pendleton
>             Fix For:
>         Attachments: dropColumn_2.diff
> Provide a way to drop a column from an existing table. Possible syntax would be:
> Feature should properly handle columns which are used in constraints, views, triggers,
indexes, etc.

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


View raw message