diff options
| author | Natalia <124304+nessita@users.noreply.github.com> | 2023-10-30 09:24:47 -0300 |
|---|---|---|
| committer | Natalia <124304+nessita@users.noreply.github.com> | 2023-10-30 13:50:20 -0300 |
| commit | 3fae5d92da84382483fe48cc62c1f57789b47196 (patch) | |
| tree | 54fb1048911c0d9597b9ac36f4ab09fa9c89365f | |
| parent | a8aa94062b108bfca473e3263473ca926fee2f42 (diff) | |
[4.2.x] Refs #30601 -- Fixed typos in docs/topics/db/transactions.txt.
Backport of 9b18af4f6f12b9d25157e0b5afc3dca198f6dd06 from main
| -rw-r--r-- | docs/topics/db/transactions.txt | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index b3388c141f..02e6e4e06a 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -213,11 +213,10 @@ Django provides a single API to control database transactions. This also applies to any other mechanism that may hold app state, such as caching or global variables. For example, if the code proactively updates data in the cache after saving an object, it's recommended to - use :ref:`transcation.on_commit <performing-actions-after-commit>` + use :ref:`transaction.on_commit() <performing-actions-after-commit>` instead, to defer cache alterations until the transaction is actually committed. - In order to guarantee atomicity, ``atomic`` disables some APIs. Attempting to commit, roll back, or change the autocommit state of the database connection within an ``atomic`` block will raise an exception. |