db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (JDO-426) NullCollectionsAndIsEmpty does not unset mapped side of relation
Date Mon, 02 Oct 2006 20:12:20 GMT
     [ http://issues.apache.org/jira/browse/JDO-426?page=all ]

Michael Bouschen reassigned JDO-426:

    Assignee: Michael Bouschen

> NullCollectionsAndIsEmpty does not unset mapped side of relation
> ----------------------------------------------------------------
>                 Key: JDO-426
>                 URL: http://issues.apache.org/jira/browse/JDO-426
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Abe White
>         Assigned To: Michael Bouschen
> org.apache.jdo.tck.query.jdoql.NullCollectionsAndIsEmpty uses its localSetUp() method
to null the projects of an Employee.  However, the Employee.projects field uses mapped-by
in its mapping, and per section 15.3 of the JDO 2 spec, that means changes to it aren't reflected
in the datastore.  To fix, add the following lines after retrieving "emp1" but before nulling
its projects in localSetUp():
>         for (Iterator itr = emp1.getProjects().iterator(); itr.hasNext();)
>             ((Project) itr.next()).removeMember(emp1);

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message