Update docs/docs/docs/01-core/database/02-transactions.md

Co-authored-by: Ben Irvin <ben@innerdvations.com>
This commit is contained in:
Marc 2023-05-23 14:02:17 +02:00 committed by GitHub
parent 13c1d0db2c
commit abfcb0c194
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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. 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. 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.