[JDO-669] TCK : RelationshipManyToManyAllRelationships.testDeleteFromMappedSide - problem with check

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JDO 3 (3.0)
• Fix Version/s: JDO 3.1-rc1
• Component/s: tck
• Assignee: Craig L Russell
• Reporter: Andy Jefferson
• Created: 19/Nov/10 19:06
• Updated: 12/Jun/15 12:47
• Resolved: 27/Nov/10 04:26

Description

Whilst this test passes with current DataNucleus (2.2 M3), I was in the process of extending its support for managed relationships, and now get this test to fail which provokes this question :-

pm.deletePersistent(proj1);
pm.flush();
deferredAssertTrue(!emp1.getProjects().contains(proj1),
ASSERTION_FAILED + testMethod, "Postcondition is false; other side of relationship not set on flush");

After the call to deletePersistent() and flush() the object "proj1" is in P_DELETED state. So when the call goes in to emp1.getProjects().contains(proj) this will interrogate the hashCode() method of Project. This is defined as

public int hashCode() {
return (int)projid;
}

But when using datastore identity "projid" is not a primary-key field, and so, as per section 5.5.6 of the spec
<spec>Read access to primary key fields is permitted. Any other access to persistent fields is not supported and might throw a JDOUserException.</spec>
So what does the implementation do ?