From 47c977c06bf9c2c50ec22ee8a55bf1bffac5b929 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20Tesa=C5=99?= <33880579+tesar-tech@users.noreply.github.com> Date: Wed, 5 Jul 2023 08:59:20 +0200 Subject: [PATCH] Adds missing ` to execute-insert-update-delete.md --- entity-framework/core/saving/execute-insert-update-delete.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/entity-framework/core/saving/execute-insert-update-delete.md b/entity-framework/core/saving/execute-insert-update-delete.md index 34f4538447..c6b607e81b 100644 --- a/entity-framework/core/saving/execute-insert-update-delete.md +++ b/entity-framework/core/saving/execute-insert-update-delete.md @@ -170,7 +170,7 @@ blog.Rating += 2; context.SaveChanges(); ``` -Each `ExecuteUpdate` call causes a single SQL `UPDATE` to be sent to the database. Since no transaction is created, if any sort of failure prevents the second `ExecuteUpdate` from completing successfully, the effects of the first one are still persisted to the database. In fact, the four operations above - two invocations of `ExecuteUpdate`, a query and `SaveChanges - each executes within its own transaction. To wrap multiple operations in a single transaction, explicitly start a transaction with : +Each `ExecuteUpdate` call causes a single SQL `UPDATE` to be sent to the database. Since no transaction is created, if any sort of failure prevents the second `ExecuteUpdate` from completing successfully, the effects of the first one are still persisted to the database. In fact, the four operations above - two invocations of `ExecuteUpdate`, a query and `SaveChanges` - each executes within its own transaction. To wrap multiple operations in a single transaction, explicitly start a transaction with : ```c# using (var transaction = context.Database.BeginTransaction())