db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6205) Allow "RENAME [...] TABLE TO" an another schema.
Date Mon, 29 Apr 2013 14:04:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644496#comment-13644496

Rick Hillegas commented on DERBY-6205:

Note that moving a table, view, type, or function may orphan dependant views and triggers.
The current, limited RENAME statement raises an error if it detects orphans. And I think that
would be fine for a first implementation of the more flexible RENAME command described by
this issue. To make this explicit, we could add the RESTRICT keyword to the end of the proposed

RENAME DERBY objectType sourceSchema.sourceObject TO targetSchema.targetObject RESTRICT

Follow-on work could add CASCADE semantics, rewriting the SQL text of dependant views and
triggers as necessary. Note that rewriting SQL text can be tricky and error-prone.

> Allow "RENAME [...] TABLE TO" an another schema.
> ------------------------------------------------
>                 Key: DERBY-6205
>                 URL: https://issues.apache.org/jira/browse/DERBY-6205
>             Project: Derby
>          Issue Type: Improvement
>            Reporter: Guillaume Chauvet
> It would be very useful to allow tables to be moved to an another schema with an extended
syntax like this :
> RENAME TABLE table-Name TO {Another schema.}new-Table-Name
> This feature will be a must-have during a database refactoring phase.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message