Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <1131185426.1133877788611.JavaMail.jira@ajax.apache.org>
Date: Tue, 6 Dec 2005 15:03:08 +0100 (CET)
From: "Michael Watzek (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Created: (JDO-229) Class DeleteCallback must not assume
 managed relationships.
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Class DeleteCallback must not assume managed relationships.
-----------------------------------------------------------

         Key: JDO-229
         URL: http://issues.apache.org/jira/browse/JDO-229
     Project: JDO
        Type: Bug
  Components: tck20  
    Reporter: Michael Watzek
 Assigned to: Michael Watzek 


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. 


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira