The Artima Developer Community
Sponsored Link

Java Buzz Forum
Using @NamedEntityGraph to load JPA entities more selectively in N+1 scenarios

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
justin cater

Posts: 19616
Nickname: justin78
Registered: Mar, 2011

Justin Cater is executive editor at Java Code Geeks
Using @NamedEntityGraph to load JPA entities more selectively in N+1 scenarios Posted: Jul 3, 2014 2:10 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by justin cater.
Original Post: Using @NamedEntityGraph to load JPA entities more selectively in N+1 scenarios
Feed Title: Java Code Geeks
Feed URL: http://feeds.feedburner.com/JavaCodeGeeks
Feed Description: Java 2 Java Developers Resource Center
Latest Java Buzz Posts
Latest Java Buzz Posts by justin cater
Latest Posts From Java Code Geeks

Advertisement

The N+1 problem is a common issue when working with ORM solutions. It happens when you set the fetchType for some @OneToMany relation to lazy, in order to load the child entities only when the Set/List is accessed. Let’s assume we have a Customer entity with two relations: a set of orders and a set […]

Read: Using @NamedEntityGraph to load JPA entities more selectively in N+1 scenarios

Topic: Spring Integration Java DSL sample – further simplification with Jms namespace factories Previous Topic   Next Topic Topic: java.util.NoSuchElementException – How to solve NoSuchElementException

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use