[ 
> Attempt to bulk-delete Employee records without nulling foreign key refere
nces from InsurancePlan
> --------------------------------------------------------------------------
-----------------------
>
>                 Key: JDO-411
>                 URL: [url]http://issues.apache.org/jira/browse/JDO-411" target="_blank">http://issues.apache.org/jira/brows.../browse/JDO-411
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>         Assigned To: Michael Bouschen
>             Fix For: JDO 2 maintenance release 1
>
>         Attachments: DeletePersistentAll.patch, JDO-411.patch
>
>
> Multiple test cases attempt to bulk delete instances of Person. However, the Emplo
yee 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 s
che
ma does not have this constraint, in order to be flexible for other database
s that will enforce the foreign key by default, some effort should be made t
o 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 relation
s are nulled. See the attached patch.
> This affects the following tests:
>  org.apache.jdo.tck.query.delete.DeletePersistentAll.testNoParametersAPI
>  org.apache.jdo.tck.query.delete.DeletePersistentAll.testNoParametersSingl
eString
>  org.apache.jdo.tck.query.delete.DeletePersistentAll.testObjectArrayParame
tersAPI
>  org.apache.jdo.tck.query.delete.DeletePersistentAll.testObjectArrayParame
tersSingleString
>  org.apache.jdo.tck.query.delete.DeletePersistentAll.testMapParametersAPI
>  org.apache.jdo.tck.query.delete.DeletePersistentAll.testMapParametersSing
leString
>  org.apache.jdo.tck.query.delete.DeleteQueryElements.testAPI
>  org.apache.jdo.tck.query.delete.DeleteQueryElements.testSingleString

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

[ Post a follow-up to this message ]