HHH-10535 Documentation: hibernate.order_updates configuration property
This commit is contained in:
parent
0e1b79d2b5
commit
13b278b663
|
@ -25,7 +25,7 @@ The following settings control this behavior.
|
||||||
It is almost never a good idea to switch from Hibernate's default implementation.
|
It is almost never a good idea to switch from Hibernate's default implementation.
|
||||||
But if you wish to, this setting would name the `org.hibernate.engine.jdbc.batch.spi.BatchBuilder` implementation to use.
|
But if you wish to, this setting would name the `org.hibernate.engine.jdbc.batch.spi.BatchBuilder` implementation to use.
|
||||||
|
|
||||||
`hibernate.order_update`::
|
`hibernate.order_updates`::
|
||||||
Forces Hibernate to order SQL updates by the entity type and the primary key value of the items being updated.
|
Forces Hibernate to order SQL updates by the entity type and the primary key value of the items being updated.
|
||||||
This allows for more batching to be used. It will also result in fewer transaction deadlocks in highly concurrent systems.
|
This allows for more batching to be used. It will also result in fewer transaction deadlocks in highly concurrent systems.
|
||||||
Comes with a performance hit, so benchmark before and after to see if this actually helps or hurts your application.
|
Comes with a performance hit, so benchmark before and after to see if this actually helps or hurts your application.
|
||||||
|
|
|
@ -787,7 +787,7 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<literal>hibernate.order_update</literal> - Forces Hibernate to order SQL updates by the
|
<literal>hibernate.order_updates</literal> - Forces Hibernate to order SQL updates by the
|
||||||
entity type and the primary key value of the items being updated. This allows for more batching
|
entity type and the primary key value of the items being updated. This allows for more batching
|
||||||
to be used. It will also result in fewer transaction deadlocks in highly concurrent systems.
|
to be used. It will also result in fewer transaction deadlocks in highly concurrent systems.
|
||||||
Comes with a performance hit, so benchmark before and after to see if this actually helps or
|
Comes with a performance hit, so benchmark before and after to see if this actually helps or
|
||||||
|
|
|
@ -63,7 +63,7 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<literal>hibernate.order_update</literal> - Forces Hibernate to order SQL updates by the
|
<literal>hibernate.order_updates</literal> - Forces Hibernate to order SQL updates by the
|
||||||
entity type and the primary key value of the items being updated. This allows for more batching
|
entity type and the primary key value of the items being updated. This allows for more batching
|
||||||
to be used. It will also result in fewer transaction deadlocks in highly concurrent systems.
|
to be used. It will also result in fewer transaction deadlocks in highly concurrent systems.
|
||||||
Comes with a performance hit, so benchmark before and after to see if this actually helps or
|
Comes with a performance hit, so benchmark before and after to see if this actually helps or
|
||||||
|
|
Loading…
Reference in New Issue