You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jdo-dev@db.apache.org by "Michael Watzek (JIRA)" <ji...@apache.org> on 2005/12/06 15:09:09 UTC

[jira] Updated: (JDO-229) Class DeleteCallback must not assume managed relationships.

     [ http://issues.apache.org/jira/browse/JDO-229?page=all ]

Michael Watzek updated JDO-229:
-------------------------------

    Attachment: JDO-229.patch

The attached patch implements the comments above.


> 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
>     Assignee: Michael Watzek
>  Attachments: JDO-229.patch
>
> 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