[ http://issues.apache.org/jira/browse/DERBY-1489?page=comments#action_12437116 ]
Daniel John Debrunner commented on DERBY-1489:
----------------------------------------------
Is it possible to commit the alter table drop column patch (in trunk) and work on the permissions
issues as a follow on?
Since it would be the trunk it could either be left as broken in SQL authorization mode, or
a quick check could be made and throw an unimplemented exception in sql auth mode. Then at
least the base code wouldbe available for others to test easily.
> 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.4, 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
|