summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKrzysztof Jagiello <me@kjagiello.com>2021-09-30 19:13:56 +0200
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2021-11-12 13:05:56 +0100
commit8d9827c06ce1592cca111e7eafb9ebe0153104ef (patch)
tree23b1a84959500c4ce21229a6f10ede06595379f0 /docs
parentadb4100e58d9ea073ee8caa454bb7c885b6a83ed (diff)
Fixed #33161 -- Enabled durability check for nested atomic blocks in TestCase.
Co-Authored-By: Adam Johnson <me@adamj.eu>
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/4.1.txt3
-rw-r--r--docs/topics/db/transactions.txt7
2 files changed, 5 insertions, 5 deletions
diff --git a/docs/releases/4.1.txt b/docs/releases/4.1.txt
index 041230b93a..7bfb527104 100644
--- a/docs/releases/4.1.txt
+++ b/docs/releases/4.1.txt
@@ -215,7 +215,8 @@ Templates
Tests
~~~~~
-* ...
+* A nested atomic block marked as durable in :class:`django.test.TestCase` now
+ raises a ``RuntimeError``, the same as outside of tests.
URLs
~~~~
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index 313aa7d188..cd58f4d68e 100644
--- a/docs/topics/db/transactions.txt
+++ b/docs/topics/db/transactions.txt
@@ -238,11 +238,10 @@ Django provides a single API to control database transactions.
is especially important if you're using :func:`atomic` in long-running
processes, outside of Django's request / response cycle.
-.. warning::
+.. versionchanged:: 4.1
- :class:`django.test.TestCase` disables the durability check to allow
- testing durable atomic blocks in a transaction for performance reasons. Use
- :class:`django.test.TransactionTestCase` for testing durability.
+ In older versions, the durability check was disabled in
+ :class:`django.test.TestCase`.
Autocommit
==========