advancedRelationships — @OneToMany, @ManyToOne, @ManyToMany, Cascade & FetchType
Why is defaulting every relationship to CascadeType.ALL a common real production mistake?
CascadeType.ALL propagates persist/merge/remove from parent to every child automatically — appropriate for genuine "part-of" ownership (an Order's LineItems), but applied broadly and by default, it can cause an accidental cascading delete on a relationship that was never meant to propagate removal, such as deleting a Customer because one of their many Orders was removed.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response