You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ddlutils-dev@db.apache.org by "Frank Hampshire (JIRA)" <ji...@apache.org> on 2008/08/04 08:09:44 UTC
[jira] Created: (DDLUTILS-223) CloneHelper does not clone onDelete
or onUpdate on ForeignKey objects
CloneHelper does not clone onDelete or onUpdate on ForeignKey objects
---------------------------------------------------------------------
Key: DDLUTILS-223
URL: https://issues.apache.org/jira/browse/DDLUTILS-223
Project: DdlUtils
Issue Type: Bug
Components: Core (No specific database)
Reporter: Frank Hampshire
Assignee: Thomas Dudziak
CloneHelper does not clone onDelete or onUpdate.
When CloneHelper clones a foreign key, it does not set the onDelete and onUpdate to the the created ForeignKey.
The solution to this seems simple enough: add
result.setOnDelete(source.getOnDelete());
result.setOnUpdate(source.getOnUpdate());
to the clone method for ForeignKey objects
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DDLUTILS-223) CloneHelper does not clone onDelete
or onUpdate on ForeignKey objects
Posted by "Thomas Dudziak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DDLUTILS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Dudziak resolved DDLUTILS-223.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.1
> CloneHelper does not clone onDelete or onUpdate on ForeignKey objects
> ---------------------------------------------------------------------
>
> Key: DDLUTILS-223
> URL: https://issues.apache.org/jira/browse/DDLUTILS-223
> Project: DdlUtils
> Issue Type: Bug
> Components: Core (No specific database)
> Reporter: Frank Hampshire
> Assignee: Thomas Dudziak
> Fix For: 1.1
>
>
> CloneHelper does not clone onDelete or onUpdate.
> When CloneHelper clones a foreign key, it does not set the onDelete and onUpdate to the the created ForeignKey.
> The solution to this seems simple enough: add
> result.setOnDelete(source.getOnDelete());
> result.setOnUpdate(source.getOnUpdate());
> to the clone method for ForeignKey objects
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.