You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/07/29 21:28:39 UTC
[jira] [Commented] (DERBY-6677) Correct Reference Manual RENAME
TABLE topic to remove foreign key prohibition
[ https://issues.apache.org/jira/browse/DERBY-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078224#comment-14078224 ]
Rick Hillegas commented on DERBY-6677:
--------------------------------------
Thanks, Kim. Looks good. Note that the work on DERBY-6672 will also lift the corresponding restriction on the renaming of columns described in rrefsqljrenamecolumnstatement.dita. Currently, that page says…
"If a view, trigger, check constraint, foreign key constraint, or generationClause of a generated column references the column, an attempt to rename it will generate an error."
That should be changed to…
"If a view, trigger, check constraint, or generationClause of a generated column references the column, an attempt to rename it will generate an error."
Thanks,
-Rick
> Correct Reference Manual RENAME TABLE topic to remove foreign key prohibition
> -----------------------------------------------------------------------------
>
> Key: DERBY-6677
> URL: https://issues.apache.org/jira/browse/DERBY-6677
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Affects Versions: 10.11.0.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-6677.diff, rrefsqljrenametablestatement.html
>
>
> It is valid to rename a table referenced by a foreign key, though Derby has not allowed it. DERBY-6672 has been filed to remove the restriction that prevents this renaming. The RENAME TABLE statement needs to reflect this change.
--
This message was sent by Atlassian JIRA
(v6.2#6252)