[#JDO-229] Class DeleteCallback must not assume managed relationships.

JDO

Class DeleteCallback must not assume managed relationships.

Created: 06/Dec/05 11:03 PM Updated: 08/Dec/05 07:10 PM

Return to search

Component/s:

tck2

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
JDO-229.patch	2005-12-06 11:07 PM	Michael Watzek	13 kB
JDO-229.patch2	2005-12-08 01:21 AM	Michael Watzek	15 kB

Resolution Date:

08/Dec/05 07:10 PM

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Michael Watzek made changes - 06/Dec/05 11:07 PM

Field	Original Value	New Value
Attachment		JDO-229.patch [ 12321170 ]

Michael Watzek made changes - 08/Dec/05 01:21 AM

Attachment

JDO-229.patch2 [ 12321204 ]

Michael Watzek made changes - 08/Dec/05 07:10 PM

Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Resolved [ 5 ]