It looks like your bulk delete query is not deleting the entries from the collection table, hence the FK constraint violation.
It looks like your bulk delete query is not deleting the entries from the collection table, hence the FK constraint violation. And while the JPA spec explicitly writes that a bulk delete is not cascaded to related entities: 4.10 Bulk Update and Delete Operations ... A delete operation only applies to entities of the specified class and its subclasses.It does not cascade to related entities. That's not exactly your case and I think that what you want to do should be supported.
You're probably facing one of the limitation of see for example: HHH-3337 - bernate disregards @JoinTable when generating bulk UPDATE/DELETE for a self-joined entity HHH-1917 - Bulk Delete on the owning side of a ManyToMany relation needs to delete corresponding rows from the JoinTable I suggest raising an issue. Workaround: use native queries to delete the collection table and then the entity table.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.