From 13b278b6639ff4614347dcf9d3ca9dd7d33dbca8 Mon Sep 17 00:00:00 2001 From: Vincent Ricard Date: Sun, 22 May 2016 18:15:18 +0200 Subject: [PATCH] HHH-10535 Documentation: hibernate.order_updates configuration property --- .../src/main/asciidoc/userguide/chapters/batch/Batching.adoc | 2 +- .../src/main/docbook/manual-old/en-US/content/bootstrap.xml | 2 +- .../main/docbook/userGuide/en-US/chapters/batch/Batching.xml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc b/documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc index fa00c7488e..eebc8f7168 100644 --- a/documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc +++ b/documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc @@ -25,7 +25,7 @@ The following settings control this behavior. 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. -`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. 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. diff --git a/documentation/src/main/docbook/manual-old/en-US/content/bootstrap.xml b/documentation/src/main/docbook/manual-old/en-US/content/bootstrap.xml index 380b6ebe18..8304654b5b 100644 --- a/documentation/src/main/docbook/manual-old/en-US/content/bootstrap.xml +++ b/documentation/src/main/docbook/manual-old/en-US/content/bootstrap.xml @@ -787,7 +787,7 @@ - hibernate.order_update - Forces Hibernate to order SQL updates by the + hibernate.order_updates - 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. Comes with a performance hit, so benchmark before and after to see if this actually helps or diff --git a/documentation/src/main/docbook/userGuide/en-US/chapters/batch/Batching.xml b/documentation/src/main/docbook/userGuide/en-US/chapters/batch/Batching.xml index 5637b632c8..a7412f9ff5 100644 --- a/documentation/src/main/docbook/userGuide/en-US/chapters/batch/Batching.xml +++ b/documentation/src/main/docbook/userGuide/en-US/chapters/batch/Batching.xml @@ -63,7 +63,7 @@ - hibernate.order_update - Forces Hibernate to order SQL updates by the + hibernate.order_updates - 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. Comes with a performance hit, so benchmark before and after to see if this actually helps or