openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1219) CLONE -Unexpected mere-cascade behavior when cascade.all/merge specified on both sides of relationships !!!
Date Thu, 06 Aug 2009 17:22:14 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Donald Woods updated OPENJPA-1219:
----------------------------------

    Fix Version/s:     (was: 2.0.0-M2)
                       (was: 1.3.0)

> CLONE -Unexpected mere-cascade behavior when cascade.all/merge specified on both sides
of relationships !!!
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1219
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1219
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 1.2.0, 2.0.0-M2
>            Reporter: eugene
>
> When cascade.all/merge is specified on both sides of relationships, and if the parent
is attached and the children are newly created entities that are being merged, the merge is
not cascading to the parent's relationships if the parent is attached.

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


Mime
View raw message