[jira] Commented: (DERBY-1490) Provide ALTER TABLE RENAME COLUMN functionality

["Bryan Pendleton (JIRA)" <de...@db.apache.org>]

    [ http://issues.apache.org/jira/browse/DERBY-1490?page=comments#action_12443162 ] 
            
Bryan Pendleton commented on DERBY-1490:
----------------------------------------

I had overlooked that Derby already supports a RENAME TABLE and RENAME INDEX statement. Given that,
I think the idea of providing a RENAME COLUMN statement makes a lot of sense.

I shall investigate a possible RENAME COLUMN statement further.

I can see that it might make sense to provide both syntaxes for renaming a column, but I can also see
that one syntax is probably plenty, so if we provide a RENAME COLUMN statement there may be no
point to having an ALTER TABLE t RENAME COLUMN c TO new_c statement.

Also, I'm not sure if there is any purpose in providing support for ALTER TABLE t RENAME TABLE t TO new_t.
That syntax seems rather awkward, and given that there is already a RENAME TABLE statement, I'm
not sure that there is any benefit to providing ALTER TABLE syntax which merely duplicates it.
So I think that part of my first patch makes no sense and should be withdrawn.

I'll be back with a new patch proposal after thinking about this some more...

> 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: derby1490_v1_needMoreTests.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