|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
08/Dec/05 07:10 PM
|
|
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.
|
|
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.
|
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Resolved
Major
Class DeleteCallback must not assume managed relationships.
