Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/JPA/GraphLoading"

(How to Optimize Object Graph Loading with JPA)
(Replacing page with '##REDIRECTEclipseLink/Examples/JPA/QueryOptimization')
Line 1: Line 1:
<div style="border:1px solid #999999;background-color:#ffffff;align:center">
+
##REDIRECT[[EclipseLink/Examples/JPA/QueryOptimization]]
<table border="0" cellpadding="5" align="center"><tr><td width="20">[[image:Catnicon.gif]]</td><td>This page is under construction.</td></tr></table>
+
</div>
+
 
+
= How to Optimize Object Graph Loading with JPA =
+
 
+
A common problem developers face when using object-relational solutions is how to optimize the loading of a graph or related objects. By default a query for the root object type and default navigation through the graph can result in a N+1 SQL performance problem. This how-to highlights EclipseLink JPA's available solutions.
+
 
+
== Example Model ==
+
 
+
== Querying without Optimizations ==
+
 
+
== JPQL JOIN FETCH ==
+
 
+
== EclipseLink Hints ==
+
 
+
EclipseLink provides additional support for joining and batch reading using query hints.
+
 
+
=== JOIN FETCH Hint ===
+
 
+
=== BATCH Hint ===
+

Revision as of 11:03, 15 June 2010

    1. REDIRECTEclipseLink/Examples/JPA/QueryOptimization

Copyright © Eclipse Foundation, Inc. All Rights Reserved.