db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Prud'hommeaux (JIRA)" <j...@apache.org>
Subject [jira] Created: (JDO-411) Attempt to bulk-delete Employee records without nulling foreign key references from InsurancePlan
Date Wed, 30 Aug 2006 01:17:22 GMT
Attempt to bulk-delete Employee records without nulling foreign key references from InsurancePlan

                 Key: JDO-411
                 URL: http://issues.apache.org/jira/browse/JDO-411
             Project: JDO
          Issue Type: Bug
          Components: tck20
    Affects Versions: JDO 2 final
            Reporter: Marc Prud'hommeaux

Multiple test cases attempt to bulk delete instances of Person. However, the Employee subclass
of Person might wind up having a non-nullable foreign key reference to Insurance or another
Employee (via the "mentor" field). While the defaut Derby TCK schema does not have this constraint,
in order to be flexible for other databases that will enforce the foreign key by default,
some effort should be made to ensure that there are no relation constraints before the bulk
deletes are attempted. This can be done by adding a nullForeignKeyReferences() method that
will manually make sure that the relations are nulled. See the attached patch.

This affects the following tests:


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


View raw message