[ http://issues.apache.org/jira/browse/DERBY-1490?page=all ]
Bryan Pendleton resolved DERBY-1490.
------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Many thanks to the reviewers for the help and good suggestions! I decided that
the patch seems to be ready and so I've committed it to subversion as revision
472708.
> 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
> Fix For: 10.3.0.0
>
> Attachments: 1490_cannot_patch.jpg, derby1490_v1_needMoreTests.diff,
> renameColumn_v2_with_tests.diff, renameColumn_v3_after_review.diff,
> renameColumn_v4_fix_error_message.diff, renameColumn_v5_with_schema_test.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
