We have stumbled upon a bug in a situation where a class A has the following associations to a class B:
- A has one B (oneToOne unidirectional)
- A has many B (oneToMany bidirectional)
Associations are with cascade remove.
We will submit a PR soon with a failing test case.
The failure is a MySQL foreign key violation exception when removing A (removals for B are executed after removals for A).