From 59720a207dabf5a939f205da7bca93c53c6a8066 Mon Sep 17 00:00:00 2001 From: sarahcaseybot Date: Thu, 26 Oct 2023 17:16:02 -0400 Subject: [PATCH] Change the default config for perTransactionIsolation to true (#2196) This was already set to true in all environments except prod last week. Now that the release has gone out and we have not seen any issues, we should feel safe turning this on in production as well. --- .../main/java/google/registry/config/files/default-config.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/main/java/google/registry/config/files/default-config.yaml b/core/src/main/java/google/registry/config/files/default-config.yaml index 97c403008..17dce56b5 100644 --- a/core/src/main/java/google/registry/config/files/default-config.yaml +++ b/core/src/main/java/google/registry/config/files/default-config.yaml @@ -193,7 +193,7 @@ hibernate: # to true, nested transactions will throw an exception. If set to false, a # transaction with the isolation override specified will still execute at the # default level (specified below). - perTransactionIsolation: false + perTransactionIsolation: true # Make 'SERIALIZABLE' the default isolation level to ensure correctness. #