You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Kevin Sutter (JIRA)" <ji...@apache.org> on 2007/05/31 21:30:15 UTC

[jira] Created: (OPENJPA-248) ForeignKey cascade delete action not working

ForeignKey cascade delete action not working
--------------------------------------------

                 Key: OPENJPA-248
                 URL: https://issues.apache.org/jira/browse/OPENJPA-248
             Project: OpenJPA
          Issue Type: Bug
          Components: jdbc
    Affects Versions: 0.9.7
            Reporter: Kevin Sutter
            Assignee: Kevin Sutter
             Fix For: 1.0.0


The code in parseForeignKey is not correct.  It is accidentally using the deleteAction setting for both the delete and update action settings.  This results in invalid SQL being generated (at least for DB2 since it doesn't like cascading updates).  This report will be used to correct these settings.  It looks like a simple case of cut-and-paste error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (OPENJPA-248) ForeignKey cascade delete action not working

Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENJPA-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Sutter resolved OPENJPA-248.
----------------------------------

    Resolution: Fixed

Fixed via svn revision 543265.

> ForeignKey cascade delete action not working
> --------------------------------------------
>
>                 Key: OPENJPA-248
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-248
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 0.9.7
>            Reporter: Kevin Sutter
>            Assignee: Kevin Sutter
>             Fix For: 1.0.0
>
>
> The code in parseForeignKey is not correct.  It is accidentally using the deleteAction setting for both the delete and update action settings.  This results in invalid SQL being generated (at least for DB2 since it doesn't like cascading updates).  This report will be used to correct these settings.  It looks like a simple case of cut-and-paste error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.