[ http://issues.apache.org/jira/browse/DERBY-1489?page=comments#action_12421193 ] Bryan Pendleton commented on DERBY-1489: ----------------------------------------
On the derby-dev list, Dan explained further: "with the dependency system it's not so much that code checks for dependent objects, more that code fires off an invalidation event (makeInvalid call) and the dependents either handle it or throw an exception to stop it." If I'm understanding this all correctly, then we don't really need to add any additional code to incorporate the new privileges feature's interaction with DROP COLUMN; we just need to add test cases to ensure that the existing dependency system is working properly. > 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.0.0, 10.1.2.1, > 10.1.3.0, 10.1.3.1 > Reporter: Bryan Pendleton > Assigned To: Bryan Pendleton > Fix For: 10.2.0.0 > > Attachments: dropColumn_2.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
