[ http://issues.apache.org/jira/browse/DERBY-1489?page=comments#action_12421197 ] Daniel John Debrunner commented on DERBY-1489: ----------------------------------------------
My guess is that some new code will need to be added in the privilege descriptor code. It probably doesn't handle an invalidation event corresponding to drop column, since drop column was not supported when that code was added. I think you are right that the existing drop column code should not need to change because of this. (famous last words :-) > 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
