[ http://issues.apache.org/jira/browse/DERBY-1489?page=all ]
Bryan Pendleton updated DERBY-1489:
-----------------------------------
Attachment: dropColumn_v4_grant_tests.diff
Attached is drop_column_v4_grant_tests.diff. This patch proposal is
updated to the latest trunk, to resolve some conflicts following the commit
of DERBY-119 and DERBY-1583. The patch also contains some new tests
which start to investigate the interaction of DROP COLUMN and column
permissions.
Unfortunately, the tests fail; the current behavior is that DROP COLUMN is not
properly aware of granted column permissions. This, I think, confirms the
suspicions that were raised earlier
http://issues.apache.org/jira/browse/DERBY-1489#action_12421197
The next step will be to investigate the dependency manager handling of
column permissions with respect to dropping a 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: 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
