db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1489) Provide ALTER TABLE DROP COLUMN functionality
Date Fri, 14 Jul 2006 18:32:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1489?page=comments#action_12421187 ] 
Bryan Pendleton commented on DERBY-1489:

This comment captures the results of a discussion on the derby-dev list regarding the interaction
of ALTER TABLE DROP COLUMN with the new security privileges functionality:

1) DROP COLUMN RESTRICT does not need to consider any additional restrictions regarding privileges.
The SQL spec does not appear to contain any text that stops the drop in restrict mode if privileges
have been granted on the column. If an object (view, trigger, etc.) is dependent on a column
level privilege then it should already be dependent on the column itself. There should be
no need to go through the list of privileges to see what objects are dependent on them.

2) DROP COLUMN needs to automatically revoke any privileges granted on the column. We need
some code in the dropColumnFromTable() method in AlterTableConstantAction which looks for
privileges granted on this column, and if there are any, automatically revoke those privileges.

3) Lastly, of course, tests of these various conditions need to be added.

> 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