Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 6, 2020
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/topics/db/transactions.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,10 +146,10 @@ Django provides a single API to control database transactions.
In this example, even if ``generate_relationships()`` causes a database
error by breaking an integrity constraint, you can execute queries in
``add_children()``, and the changes from ``create_parent()`` are still
there. Note that any operations attempted in ``generate_relationships()``
will already have been rolled back safely when ``handle_exception()`` is
called, so the exception handler can also operate on the database if
necessary.
there and bound to the same transaction. Note that any operations attempted
in ``generate_relationships()`` will already have been rolled back safely
when ``handle_exception()`` is called, so the exception handler can also
operate on the database if necessary.

.. admonition:: Avoid catching exceptions inside ``atomic``!

Expand Down