Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <20610982.1189352609932.JavaMail.jira@brutus>
Date: Sun, 9 Sep 2007 08:43:29 -0700 (PDT)
From: "Andy Jefferson (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Commented: (JDO-521) Create tests for relationship mapping
 (spec section 15.3)
In-Reply-To: <18770819.1187734830541.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JDO-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526000 ] 

Andy Jefferson commented on JDO-521:
------------------------------------

The negative test I was expecting to find was where you set up something like this

Employee emp1 = new FullTimeEmployee();
MedicalInsurance ins1 = new MedicalInsurance();
Employee emp2 = new PartTimeEmployee();
emp1.setMedicalInsurance(ins1);
ins1.setEmployee(emp2);
pm.makePersistent(emp1);

so in a single user operation inconsistent data is provided (hence independent of when data is flushed to the datastore) hence an expected JDOUserException. Does this exist ?

> Create tests for relationship mapping (spec section 15.3)
> ---------------------------------------------------------
>
>                 Key: JDO-521
>                 URL: https://issues.apache.org/jira/browse/JDO-521
>             Project: JDO
>          Issue Type: Test
>          Components: tck2
>    Affects Versions: JDO 2 maintenance release 1
>            Reporter: Michelle Caisse
>            Assignee: Michelle Caisse
>         Attachments: JDO-521.patch
>
>
> We need a set of tests to test that an implementation syncs both sides of a relationship on flush().

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