Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3313846
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T22:09:47+00:00 2026-05-17T22:09:47+00:00

I have a domain object that contains another domain object; call them A and

  • 0

I have a domain object that contains another domain object; call them A and B. B contains a blob (an image file) which can be large. As long as I am only dealing with one A at a time having B on A isn’t a concern. However, sometimes I’ll be dealing with thousands of A in which carrying around the blob on B causes heap to run out. When I am dealing with so many A I really don’t need B anyway.

Is there some way of telling Hibernate to ignore this property for a particular call? Should I just make B transient and deal with updating/deleting manually in this case?

Right now to get around this problem I use a SQL query to pull all the ids I want then iterate over that list getting each domain object out, doing what I need, then evicting it.

Also, I can’t lazy load B because I’m in a servlet environment so my Hibernate session is closed before I access the properties in most cases.

@Entity
@Table(name="A")
public class A {

  private Long id

  @OneToOne(fetch = FetchType.EAGER, cascade = { CascadeType.ALL }, orphanRemoval = true)
  @JoinColumn(name = "a_id", referencedColumnName = "b_id", nullable = true)
  @NotFound(action = NotFoundAction.IGNORE)
  private B b

  ...getters and setters
}

@Entity
@Table(name="B")
public class B {
  private Long id;
  private byte[] blob;

  ...getters and setters
}

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T22:09:47+00:00Added an answer on May 17, 2026 at 10:09 pm

    Is there some way of telling Hibernate to ignore this property for a particular call? Should I just make B transient and deal with updating/deleting manually in this case?

    One option would be to use lazy property fetching (this requires bytecode instrumentation, refer to the documentation). So you could map B like this:

    @Entity
    @Table(name="B")
    public class B {
      @Id
      private Long id;
    
      @Basic(fetch = FetchType.LAZY)
      @Lob
      private byte[] blob;
    
      // getters and setters
    }
    

    And, as documented:

    You can force the usual eager fetching of properties using fetch all properties in HQL.

    Another option would be to use an alternative version of A (A’) without the B, for this special use case.

    References

    • Hibernate Annotations Reference Guide
      • 2.2.2. Mapping simple properties
    • Hibernate Core Reference Guide
      • 20.1.8. Using lazy property fetching
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.