From abfcb0c194c9fcd5fbb059254aef277f4c3feba3 Mon Sep 17 00:00:00 2001 From: Marc Date: Tue, 23 May 2023 14:02:17 +0200 Subject: [PATCH] Update docs/docs/docs/01-core/database/02-transactions.md Co-authored-by: Ben Irvin --- docs/docs/docs/01-core/database/02-transactions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/docs/docs/01-core/database/02-transactions.md b/docs/docs/docs/01-core/database/02-transactions.md index 74d9d320fd..c05c474d16 100644 --- a/docs/docs/docs/01-core/database/02-transactions.md +++ b/docs/docs/docs/01-core/database/02-transactions.md @@ -100,3 +100,5 @@ Transactions should not be used for operations that are not dependent on each ot Performing multiple operations within a transaction can lead to locking, which can block the execution of transactions from other processes until the original transaction is complete. Furthermore, transactions can stall if they are not committed or rolled back appropriately. + +For example, if a transaction is opened but there is a path in your code that does not close it, the transaction will be left open indefinitely and could cause instability until your server is restarted and the connection is forced to close. These issues can be difficult to debug, so use transactions with care in the cases they are necessary.