[ http://issues.apache.org/jira/browse/DERBY-1489?page=comments#action_12436655 ]
Bryan Pendleton commented on DERBY-1489:
----------------------------------------
I copied this comment from a different email discussion, involving some
possible interactions between DERBY-655, DERBY-1854, and this bug:
> There are a number of code paths in the server that use the
> "bait/switch" method. Off the top of my head: some alter table
> modify column paths, maybe drop column, bulk load to an empty table.
> Were these also broken for this problem? Is the code to do the
> syscat update shared, and thus this fixes all of them? Probably
> worth adding some test cases.
So, the current overall status of this issu is:
1) Need to write logic to drop GRANTed column permissions when dropping a column
2) Need to add test cases to see if the DERBY-655 regression affects DROP COLUMN
> 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: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.1.0, 10.1.2.1, 10.1.3.0, 10.1.3.1
> Reporter: Bryan Pendleton
> Assigned To: Bryan Pendleton
> Attachments: drop_column_v5_grant_tests.diff, dropColumn_2.diff, dropColumn_v3_view_drop.diff,
dropColumn_v4_grant_tests.diff
>
>
> Provide a way to drop a column from an existing table. Possible syntax would be:
> ALTER TABLE tablename DROP COLUMN columnname CASCADE / RESTRICT;
> 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
|