Fixed #31423 -- Clarified nested atomic() example.

This commit is contained in:
Simon Charette 2020-04-04 20:28:54 +02:00 committed by Mariusz Felisiak
parent 6fbce45b03
commit fa5e7e46d8
1 changed files with 4 additions and 4 deletions

View File

@ -146,10 +146,10 @@ Django provides a single API to control database transactions.
In this example, even if ``generate_relationships()`` causes a database In this example, even if ``generate_relationships()`` causes a database
error by breaking an integrity constraint, you can execute queries in error by breaking an integrity constraint, you can execute queries in
``add_children()``, and the changes from ``create_parent()`` are still ``add_children()``, and the changes from ``create_parent()`` are still
there. Note that any operations attempted in ``generate_relationships()`` there and bound to the same transaction. Note that any operations attempted
will already have been rolled back safely when ``handle_exception()`` is in ``generate_relationships()`` will already have been rolled back safely
called, so the exception handler can also operate on the database if when ``handle_exception()`` is called, so the exception handler can also
necessary. operate on the database if necessary.
.. admonition:: Avoid catching exceptions inside ``atomic``! .. admonition:: Avoid catching exceptions inside ``atomic``!