openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar (JIRA)" <j...@apache.org>
Subject [jira] Closed: (OPENJPA-527) Merge of new one-to-many list only persists last element.
Date Tue, 17 Jun 2008 20:19:46 GMT

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

Pinaki Poddar closed OPENJPA-527.
---------------------------------

    Resolution: Fixed

The attached test passes with 1.2.0-SNAPSHOT.


> Merge of new one-to-many list only persists last element.
> ---------------------------------------------------------
>
>                 Key: OPENJPA-527
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-527
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.0.2
>            Reporter: Gil Markham
>            Assignee: Pinaki Poddar
>            Priority: Critical
>             Fix For: 1.0.3
>
>         Attachments: mergetest.tgz, mergetest.tgz
>
>
> If a transient new object is merged containing a one-to-many (with elementjoincolumn)
list of transient new objects the last object in the list is the only object persisted.  This
functionality has changed since 1.0.1 as the same code worked properly with that version.
> Calling persist using an equivalent object works properly but this should work in both
cases.
> I'll attach a tgz of a maven project that illustrates the problem.  The project uses
hsqldb internally and should run stand alone without anything but maven and java installed.

-- 
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