Class DeleteCallback must not assume managed relationships.

• Key: JDO-229
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Michael Watzek
• Reporter: Michael Watzek
• Component/s: tck2

Description

There is a portability issue with test case DeleteCallback:

The test case assumes that a JDO implementation supports managed relationships, because it deletes instances which are referenced by other instances. Given that the relationships are represented by foreign keys in the database for which the delete rule is specified as RESTRICT, the test will cause errors for JDO implementations which do not support managed relationships, because it does not nullify those references explicitely,

In order to make the test case portable, it should explicitely nullify references to all deleted objects first. Afterwards, it should call Query.deletePersistentAll.

Comments

[Michael Watzek]

The attached patch implements the comments above.

Just a few comments.

1. The line:
                lifecycleVerifyer = new LifecycleVerifier(result);
should probably also change the name of the variable, to:
                lifecycleVerifier = new LifecycleVerifier(result);

2. The code to clear relationships for the deletePersistentAll problem doesn't appear to solve the issue. The issue is not relationships FROM the employees, it's relationships TO the employee that are represented by database constraints.

+ * If instances are employees, then all relationships are cleared.
* If instances are employees, relationships to the employee are cleared.

+ employee.setDentalInsurance(null);
employee.getDentalInsurance.setEmployee(null);
+ employee.setMedicalInsurance(null);
employee.getMedicalInsurance.setEmployee(null);
+ employee.setDepartment(null);
don't need anything
+ employee.setFundingDept(null);
don't need anything
+ employee.setManager(null);
don't need anything
+ employee.setMentor(null);
employee.getMentor().setProtege(null);
+ employee.setHradvisor(null);
don't need anything
+ employee.setReviewedProjects(new HashSet());
foreach Project p in employee.getReviewedProjects(){p.removeReviewer(employee);}
+ employee.setProjects(new HashSet());
foreach Project p in employee.getProjects() {p.removeMember(employee);}

[Michael Watzek]

The second patch implements the comments above.

[Michael Bouschen]

The second patch looks good.

[Michael Watzek]

The second patch has been checked in (revision 355060).