Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify subselect fetching 

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@7490 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Christian Bauer 2005-07-15 08:21:50 +00:00
parent 545bb859b7
commit 91c3595bfd
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
reference/en/modules/performance.xml
View File

@ -155,7 +155,7 @@ Integer accessLevel = (Integer) permissions.get("accounts"); // Error!]]></prog
</sect2> </sect2>
<sect2 id="performance-fetching-custom" revision="3"> <sect2 id="performance-fetching-custom" revision="4">
<title>Tuning fetch strategies</title> <title>Tuning fetch strategies</title>
<para> <para>
@ -172,7 +172,7 @@ Integer accessLevel = (Integer) permissions.get("accounts"); // Error!]]></prog
<programlisting><![CDATA[<many-to-one name="mother" class="Cat" fetch="join"/>]]></programlisting> <programlisting><![CDATA[<many-to-one name="mother" class="Cat" fetch="join"/>]]></programlisting>
<para> <para>
The fetch strategy defined in the mapping document affects: The <literal>fetch</literal> strategy defined in the mapping document affects:
</para> </para>
<itemizedlist> <itemizedlist>
@ -184,7 +184,6 @@ Integer accessLevel = (Integer) permissions.get("accounts"); // Error!]]></prog
<listitem> <listitem>
<para> <para>
retrieval that happens implicitly when an association is navigated retrieval that happens implicitly when an association is navigated
(lazy fetching)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
@ -192,8 +191,19 @@ Integer accessLevel = (Integer) permissions.get("accounts"); // Error!]]></prog
<literal>Criteria</literal> queries <literal>Criteria</literal> queries
</para> </para>
</listitem> </listitem>
<listitem>
<para>
HQL queries if <literal>subselect</literal> fetching is used
</para>
</listitem>
</itemizedlist> </itemizedlist>
<para>
No matter what fetching strategy you use, the defined non-lazy graph is guaranteed
to be loaded into memory. Note that this might result in several immediate selects
being used to execute a particular HQL query.
</para>
<para> <para>
Usually, we don't use the mapping document to customize fetching. Instead, we Usually, we don't use the mapping document to customize fetching. Instead, we
keep the default behavior, and override it for a particular transaction, using keep the default behavior, and override it for a particular transaction, using