|[eclipselink-dev] Cascade Deletes through ManyToMany|
This issue exists beyond cascade delete as even if the user deleted the two object manually the constraint violation would still occur.
The easiest solution is to simply report the dependency on writable ManyToMany mappings but this may break previous applications that were dependent on the pseudo random ordering that EclipseLink used previously (some of our testing breaks).
Special code could be added to update the collection on cascade remove but there's no guarantee that the update may not be optimized out at some later date and it does not solve this issue when cascade delete is not used or JPA is not used.
I recommend we update the dependency. --Gordon
Back to the top