Hi, I’m refactoring a project after remove enable_lazy_load_no_trans, and I’m following the best practices from Vlad’s blog. I read the article: https://vladmihalcea.com/the-best-way-to-map-a-onetoone-relationship-with-jpa-and-hibernate/ and it suggests that the best way is mapping an unidirection…

In my project I have a lot of @OneToOne bidirectional You don’t need those. If you use @MapsId, you don’t need bidirectional associations. Just remove them and save yourself some extra queries.

Thank you for your reply. I know that, but my mainly two doubts are how to proceed with the situations that I described. I mean, if a removed the OneToOne bidirectional, should I save all the associations like I ask? And about the situation of optional entities that I always have to check if they…

When you persist, you need to call persist, not merge. If you don’t use bidirectional associations, then the parent must be persisted first, then the child. As for the other question, I don’t really understand what you are asking. Try to ask very clear questions which focus on a single problem at …

[image] vlad: If you don’t use bidirectional associations, then the parent must be persisted first, then the child. Ok, I understand now. About the second question, I asked because it refer to the same changing. Most of the OneToOne bidirectional that I have, define the behavior of the enti…

[image] guibernardi: My question is: what’s a good practice, turn it in a boolean mark in my parent to know when I need to fetch them instead of check if the association is null or any other practice? That sounds like a hack since you are altering the DB schema with fields that have no meanin…

Looks like you are trying to do an Joined inheritance model by hand… PessoaFisica extends Pessoa PessoaJuridica extends Pessoa with an @Inheritance(strategy = InheritanceType.JOINED) and maybe even make Pessoa abstract if it can’t be instantiated could probably do what you are trying to code man…

Yep, you get it. My Pessoa (Person) entity can be Cliente (Customer), Fornecedor (Supplier), Transportadora (Shipping Company), Vendedor (Salesman). But not only one of them, a Pessoa (Person), can be one or more “types”. You p3consulting can be a Customer and Supplier for me. I know that is wron…

Like you can use the code like this: @JoinColumn(name=“Ingredient1”, insertable = true, updatable = true, nullable = true) @Fetch(FetchMode.JOIN) private RecipeIngredients ingredient1; that will not execute the extra query. if you are using inheritance mapping: @Inheritance(strategy = Inherit…

Customer and Supplier are not types of Person but type of Relationships between Person. Shipping Company, Salesman, … are types of Activities. You are missing some taxonomies in your model…

Best OneToOne mapping recommendation

Hibernate ORM

p3consulting May 4, 2018, 5:18am 13

… but they should not… but this is out of scope for an Hibernate forum…
it’s more related to semantic, ontology and modelization…

Topic		Replies	Views
Mapping unidirectional one-to-one relations correctly Hibernate ORM	8	3442	August 15, 2024
First of two OneToOne Mappings fails Hibernate ORM	7	958	October 24, 2022
Hibernate N+1 query issue when fetching @OneToOne associations with JPA Criteria and @LazyToOne Hibernate ORM	6	9889	February 4, 2020
OneToOne(LAZY) links produce different queries by findOneById for similar entities Hibernate ORM	1	71	June 3, 2025
Unidirectional vs bidirectional ManyToOne Hibernate ORM	2	4466	June 21, 2018

Best OneToOne mapping recommendation

Related topics