# Decision to create an additional table for one to many

**URL:** <https://discourse.hibernate.org/t/decision-to-create-an-additional-table-for-one-to-many/354>\
**Category:** Hibernate ORM\
**Created:** [March 15, 2018, 10:10am UTC](https://discourse.hibernate.org/t/decision-to-create-an-additional-table-for-one-to-many/354 "2018-03-15T10:10:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![awood](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@awood](https://discourse.hibernate.org/u/awood)\
**Post date:** [March 15, 2018, 10:10am UTC](https://discourse.hibernate.org/t/decision-to-create-an-additional-table-for-one-to-many/354/1 "2018-03-15T10:10:30Z")

</div>

Why does hibernate create an additional mapping table for the one-to-many relationship, as SQL really doesn’t need this?

---

<div class="post-metadata">

**Author:** ![vlad](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.hibernate.org/vlad/32/658_2.png) [@vlad](https://discourse.hibernate.org/u/vlad)\
**Post date:** [March 15, 2018, 10:31am UTC](https://discourse.hibernate.org/t/decision-to-create-an-additional-table-for-one-to-many/354/2 "2018-03-15T10:31:09Z")

</div>

It only does that for unidirectional OneToMany association that don’t have a @JoinColumn.

Hoever, you are better off using bidirectional associations. For more details, check out [this article](https://vladmihalcea.com/the-best-way-to-map-a-onetomany-association-with-jpa-and-hibernate/).

---

<div class="post-metadata">

**Author:** ![awood](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@awood](https://discourse.hibernate.org/u/awood)\
**Post date:** [March 15, 2018, 11:06am UTC](https://discourse.hibernate.org/t/decision-to-create-an-additional-table-for-one-to-many/354/3 "2018-03-15T11:06:09Z")

</div>

Thanks, that was a good article and helps bridge the gap between SQL relationships and application behaviour.  
Ta