How can I make a JPA OneToOne relation lazy

by

First off, some clarifications to KLE‘s answer:

  1. Unconstrained (nullable) one-to-one association is the only one that can not be proxied without bytecode instrumentation. The reason for this is that owner entity MUST know whether association property should contain a proxy object or NULL and it can’t determine that by looking at its base table’s columns due to one-to-one normally being mapped via shared PK, so it has to be eagerly fetched anyway making proxy pointless. Here’s a more detailed explanation.

  2. many-to-one associations (and one-to-many, obviously) do not suffer from this issue. Owner entity can easily check its own FK (and in case of one-to-many, empty collection proxy is created initially and populated on demand), so the association can be lazy.

  3. Replacing one-to-one with one-to-many is pretty much never a good idea. You can replace it with unique many-to-one but there are other (possibly better) options.

Rob H. has a valid point, however you may not be able to implement it depending on your model (e.g. if your one-to-one association is nullable).

Now, as far as original question goes:

A) @ManyToOne(fetch=FetchType.LAZY) should work just fine. Are you sure it’s not being overwritten in the query itself? It’s possible to specify join fetch in HQL and / or explicitly set fetch mode via Criteria API which would take precedence over class annotation. If that’s not the case and you’re still having problems, please post your classes, query and resulting SQL for more to-the-point conversation.

B) @OneToOne is trickier. If it’s definitely not nullable, go with Rob H.’s suggestion and specify it as such:

@OneToOne(optional = false, fetch = FetchType.LAZY)

Otherwise, if you can change your database (add a foreign key column to owner table), do so and map it as “joined”:

@OneToOne(fetch = FetchType.LAZY)
@JoinColumn(name="other_entity_fk")
public OtherEntity getOther()

and in OtherEntity:

@OneToOne(mappedBy = "other")
public OwnerEntity getOwner()

If you can’t do that (and can’t live with eager fetching) bytecode instrumentation is your only option. I have to agree with CPerkins, however – if you have 80!!! joins due to eager OneToOne associations, you’ve got bigger problems then this 🙂

More Related Contents:

  1. Why is Hibernate Open Session in View considered a bad practice?
  2. How to convert a Hibernate proxy to a real entity object
  3. Java: Hibernate @OneToOne mapping
  4. Clarifying terminology – What does “hydrating” a JPA or Hibernate entity mean when fetching the entity from the DB
  5. Difference between FetchType LAZY and EAGER in Java Persistence API?
  6. Confusion: @NotNull vs. @Column(nullable = false) with JPA and Hibernate
  7. What is “the inverse side of the association” in a bidirectional JPA OneToMany/ManyToOne association?
  8. No Dialect mapping for JDBC type: 1111
  9. Hibernate one-to-one: getId() without fetching entire object
  10. Difference between @OneToMany and @ElementCollection?
  11. What is the difference between CascadeType.REMOVE and orphanRemoval in JPA?
  12. @GeneratedValue polymorphic abstract superclass over MySQL
  13. Transaction marked as rollback only: How do I find the cause
  14. Hibernate: best practice to pull all lazy collections
  15. JPA: Implementing Model Hierarchy – @MappedSuperclass vs. @Inheritance
  16. How to use multiple JOIN FETCH in one JPQL query
  17. JPA OneToMany and ManyToOne throw: Repeated column in mapping for entity column (should be mapped with insert=”false” update=”false”)
  18. Hibernate generates negative id values when using a sequence
  19. GenerationType.AUTO vs GenerationType.IDENTITY in hibernate
  20. How to prevent SQL Injection with JPA and Hibernate?
  21. Native query with named parameter fails with “Not all named parameters have been set”
  22. Specifying an Index (Non-Unique Key) Using JPA
  23. Hibernate: Create Mysql InnoDB tables instead of MyISAM
  24. @BatchSize a smart or stupid use?
  25. Spring Data JPA and Exists query
  26. Hibernate throws strange error: Class is not mapped
  27. Error creating bean with name ‘entityManagerFactory
  28. When to use DiscriminatorValue annotation in hibernate
  29. How to map one class with multiple tables in Hibernate/javax.persistance?
  30. JPA: difference between @JoinColumn and @PrimaryKeyJoinColumn?

Leave a Comment