|
Steve, yes, it's about cleaning up orphaned rows on the association table.
HHH-1917
added support to automatically delete the rows, but in the wrong spot. If the owning entity is not joined-subclass, union-subclass, or with secondary tables, the
HHH-1917
's solution on MultiTableDeleteExecutor fails. That's why I was suggesting moving it.
However, I get the point about "cascade delete" – maybe we should just focus on that.
|
