How do you model @ManyToOne versus @OneToMany without creating a mapping mess?
PICTURE THIS: SQL JOIN
Simple meaning
The many side usually owns the foreign key with @ManyToOne, which is the side you need for inserts.
WHY — JPA instead of guessing?
Why interviewers care about JPA:
contrast on JPA, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1The many side usually
owns the foreign key with @ManyToOne, which is the side you need for inserts.
- 2@OneToMany mappedBy points at
that field so Hibernate does not create a join table you did not want.
- 3Bidirectional graphs are convenient
in memory but easy to serialize into infinite JSON, so keep API mapping one-directional.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
The many side usually owns the foreign key with @ManyToOne, which is the side you need for inserts. @OneToMany mappedBy points at that field so Hibernate does not create a join table you did not want.