db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Kartha (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1490) Provide ALTER TABLE RENAME COLUMN functionality
Date Sat, 28 Oct 2006 06:01:19 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1490?page=comments#action_12445341 ] 
            
Rajesh Kartha commented on DERBY-1490:
--------------------------------------

I tried to applying the patch in my Eclipse env but only the sqlgrammar.jj could be successfully
patched. For the remaining files it complained - I will attach a screen shot  for those. Wonder
if anyone else ran into this.

Anyways,   I was able to look at the functionality and things worked fine - could not run
the tests though.  Regarding the  questions you raised:

1) I  think    RENAME COLUMN t.c1 to c2 seems to be more appropriate. This, as you righly
pointed out earlier, seems to be consistent
with RENAME TABLE/INDEX. Of the databases  have worked on - I think  MySQL and Informix behaves
in the same way.

2)  I was wondering shouldn't  there be some tests  using the sqlAuthorization mode too. I
manually tried them - a user with select only privileges attempting to rename the column etc.
and those seem to work fine.


> 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
>
>
> 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

        

Mime
View raw message