document fetch all properties
git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@6383 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
parent
918311093e
commit
f882362299
|
@ -148,13 +148,23 @@
|
|||
</para>
|
||||
|
||||
<para>
|
||||
Note that, in the current implementation, only one collection role may be fetched
|
||||
in a query (everything else would be non-performant). Note also that the
|
||||
<literal>fetch</literal> construct may not be used in queries called using
|
||||
Note that, in the current implementation, only one collection role may be join fetched
|
||||
in a query (more than one role will usually result in a cartesian product). Note also
|
||||
that the <literal>fetch</literal> construct may not be used in queries called using
|
||||
<literal>scroll()</literal> or <literal>iterate()</literal>. Finally, note that
|
||||
<literal>full join fetch</literal> and <literal>right join fetch</literal> are not meaningful.
|
||||
<literal>full join fetch</literal> and <literal>right join fetch</literal> are not
|
||||
meaningful.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If you are using property-level lazy fetching (with bytecode instrumentation), it is
|
||||
possible to force Hibernate to fetch the lazy properties immediately (in the first
|
||||
query) using <literal>fetch all properties</literal>.
|
||||
</para>
|
||||
|
||||
<programlisting><![CDATA[from Document fetch all properties order by name]]></programlisting>
|
||||
<programlisting><![CDATA[from Document doc fetch all properties where lower(doc.name) like '%cats%']]></programlisting>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="queryhql-select">
|
||||
|
|
Loading…
Reference in New Issue