http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DDC-678 Doctrine 2 - ORM <p>OneToMany/OneToOne associations together with an onDelete=CASCADE schema generation hint on the @JoinColumn and appropriate foreign key constraints can potentially result in a corrupt UoW if the associated objects are already managed. We need to add tests for such scenarios and settle on a well-defined behavior in such cases.</p> DDC-678

OneToMany/OneToOne + onDelete=CASCADE may corrupt UoW.

Improvement Major Open Unresolved All Roman S. Borschel Roman S. Borschel Sat, 10 Jul 2010 07:07:01 +0000 Sun, 5 Jun 2011 15:15:44 +0000 0 0 <p>I think to preserve the semantics the following has to happen:</p> <p>"on-delete" =&gt; "cascade" has to implicitly set cascade = remove. This hurts performance of course vs just using the on-delete, however it won't corrupt the UoW.</p> <p>Not entirely would it hurt performance, you could check if on-delete =&gt; cascade is set. If this is the case you wouldnt need to do an explicit remove using the UnitOfWorks cascade.</p> <p>Changed to improvement</p>