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

HHH-5149 fix text not wrapping up in html rendering 

Was due to a itemizedlist embedded in a para

git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@19710 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Emmanuel Bernard 2010-06-10 16:20:43 +00:00
parent 1eaf80e3a9
commit 74a5e4b405
1 changed files with 31 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

60
documentation/manual/src/main/docbook/en-US/content/basic_mapping.xml
View File

@ -2308,8 +2308,8 @@ class Person {
<listitem>
<para><literal>optimizer</literal> (optional - defaults to
<literal></literal>): See <xref
linkend="mapping-declaration-id-enhanced-optimizers" /></para>
<literal>??</literal>): See <xref
linkend="mapping-declaration-id-enhanced-optimizers" />.</para>
</listitem>
</itemizedlist></para>
@ -2323,35 +2323,37 @@ class Person {
exhausted your in-memory value group. This is the role of the
pluggable optimizers. Currently only the two enhanced generators
(<xref linkend="mapping-declaration-id-enhanced" /> support this
operation. <itemizedlist spacing="compact">
<listitem>
<para><literal>none</literal> (generally this is the default
if no optimizer was specified): this will not perform any
optimizations and hit the database for each and every
request.</para>
</listitem>
operation. </para>
<listitem>
<para><literal>hilo</literal>: applies a hi/lo algorithm
around the database retrieved values. The values from the
database for this optimizer are expected to be sequential. The
values retrieved from the database structure for this
optimizer indicates the "group number". The
<literal>increment_size</literal> is multiplied by that value
in memory to define a group "hi value".</para>
</listitem>
<itemizedlist spacing="compact">
<listitem>
<para><literal>none</literal> (generally this is the default if
no optimizer was specified): this will not perform any
optimizations and hit the database for each and every
request.</para>
</listitem>
<listitem>
<para><literal>pooled</literal>: as with the case of
<literal>hilo</literal>, this optimizer attempts to minimize
the number of hits to the database. Here, however, we simply
store the starting value for the "next group" into the
database structure rather than a sequential value in
combination with an in-memory grouping algorithm. Here,
<literal>increment_size</literal> refers to the values coming
from the database.</para>
</listitem>
</itemizedlist></para>
<listitem>
<para><literal>hilo</literal>: applies a hi/lo algorithm around
the database retrieved values. The values from the database for
this optimizer are expected to be sequential. The values
retrieved from the database structure for this optimizer
indicates the "group number". The
<literal>increment_size</literal> is multiplied by that value in
memory to define a group "hi value".</para>
</listitem>
<listitem>
<para><literal>pooled</literal>: as with the case of
<literal>hilo</literal>, this optimizer attempts to minimize the
number of hits to the database. Here, however, we simply store
the starting value for the "next group" into the database
structure rather than a sequential value in combination with an
in-memory grouping algorithm. Here,
<literal>increment_size</literal> refers to the values coming
from the database.</para>
</listitem>
</itemizedlist>
</section>
</section>