Скачать или смотреть Resolving Hibernate Unidirectional One-to-Many Associations: A Guide to Foreign Keys

Learn how to solve the issue of `foreign key` updates in unidirectional `@ OneToMany` associations with `Hibernate` without using a bidirectional relationship or deferrable constraints.
---
This video is based on the question https://stackoverflow.com/q/71020174/ asked by the user 'peshi' ( https://stackoverflow.com/u/4233068/ ) and on the answer https://stackoverflow.com/a/71022982/ provided by the user 'Chris' ( https://stackoverflow.com/u/496099/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Hibernate unidirectional @ OneToMany association triggers updates of foreign keys

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Resolving Hibernate Unidirectional One-to-Many Associations: A Guide to Foreign Keys

When working with Hibernate and Java Persistence API (JPA), developers may occasionally encounter challenges with managing associations, particularly when dealing with unidirectional @ OneToMany mappings. A common scenario arises when setting up foreign keys within these associations, leading to foreign key update issues due to unique constraints. This guide explores a specific problem, presents a straightforward solution, and breaks down the steps necessary to implement that solution.

The Problem at Hand

In the context of the given entities, let's understand the situation:

You have a Type entity that is associated with multiple Translation entities using a unidirectional @ OneToMany association.

When creating new translations for a type, Hibernate attempts to insert the translations with null values for the foreign key columns (BOUND_TO_ID and BOUND_TO_CLASS).

There is a unique constraint on the combination of BOUND_TO_ID, BOUND_TO_CLASS, and locale, which prevents the insertion of translations in the same locale across different types.

Because of this conflict, it becomes impossible to create various translations without either loosening the unique constraint or establishing a bidirectional association. Fortunately, there are ways to circumvent this issue while maintaining the integrity of your data model.

The Solution: Updating Mappings for Better Control

There are a couple of approaches to solve this problem, allowing you to handle your translations without having to alter the database constraints or modify the relationship direction:

1. Employ a Bidirectional Association (Optional)

While the objective is to avoid a bidirectional relationship, it’s worth mentioning this common solution for completeness:

[[See Video to Reveal this Text or Code Snippet]]

This approach automatically populates the foreign key values, but you specifically want to avoid it.

2. Manual Mapping of Foreign Keys

Instead, consider manually mapping the BOUND_TO_ID and BOUND_TO_CLASS fields within the Translation entity while allowing operations to remain read-only in the Type entity:

Update the Translation Entity

[[See Video to Reveal this Text or Code Snippet]]

By explicitly managing these columns, you take control of how the translations are created and associated with the Type.

Update the Type Entity's Relationship

Mark the translation mapping in the Type entity as read-only to prevent Hibernate from trying to manage these foreign key fields automatically:

[[See Video to Reveal this Text or Code Snippet]]

3. Creating a Translation Instance

When persisting the Type entity, ensure you follow the correct steps for creating associated translations:

Persist the Type Instance: Use the EntityManager to first persist the Type and flush the entity manager context, which will assign the generated ID.

[[See Video to Reveal this Text or Code Snippet]]

Set Translation Fields: After obtaining the ID from the persisted Type, set the objectId and objectType in your Translation instances accordingly.

Persist Translations: Finally, save the translations to be linked to the persisted Type.

Conclusion

By carefully managing how you map and persist your entity relationships in Hibernate, it is possible to work effectively with unidirectional @ OneToMany associations without falling into pitfalls associated with foreign key updates and unique constraints. Following the steps laid out in this guide will empower you to maintain the integrity of your database schema according to your application requirements.

With this approach, you can confidently ma