[ http://issues.apache.org/jira/browse/DERBY-1490?page=comments#action_12447519 ] Bryan Pendleton commented on DERBY-1490: ----------------------------------------
Thanks to all for the review (no, you're not being a pain at all!) Good catch on the error message; it's easy to fix, and I'll revise the patch to say RENAME COLUMN not ALTER TABLE. Rajesh, I think the suggestion about RENAME CONSTRAINT is intriguing, and I think it is worth filing for future investigation. I don't know how often users with to be able to rename a constraint, but I agree that having to drop and re-add it just in order to rename it is awkward. Army, regarding the sqlAuthorization issue, I don't have a definite resolution. For now, the tests in lang/altertable.sql run only with sqlAuthorization=true. > Provide ALTER TABLE RENAME COLUMN functionality > ----------------------------------------------- > > Key: DERBY-1490 > URL: http://issues.apache.org/jira/browse/DERBY-1490 > 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.6, 10.1.2.1, > 10.1.3.1 > Reporter: Bryan Pendleton > Assigned To: Bryan Pendleton > Attachments: 1490_cannot_patch.jpg, derby1490_v1_needMoreTests.diff, > renameColumn_v2_with_tests.diff, renameColumn_v3_after_review.diff > > > Provide a way to rename a column in an existing table. Possible syntax could > be: > ALTER TABLE tablename RENAME COLUMN oldcolumn TO newcolumn; > Feature should properly handle the possibility that the column is currently > used in constraints, views, indexes, triggers, 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
