mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Used :pep: role in various docs.
This commit is contained in:
parent
f9d13a1b5a
commit
a9337b4add
7 changed files with 20 additions and 22 deletions
|
@ -369,8 +369,8 @@ etc.), this should be fine. If it's not (if your follow-up action is so
|
|||
critical that its failure should mean the failure of the transaction itself),
|
||||
then you don't want to use the :func:`on_commit` hook. Instead, you may want
|
||||
`two-phase commit`_ such as the :ref:`psycopg Two-Phase Commit protocol support
|
||||
<psycopg2:tpc>` and the `optional Two-Phase Commit Extensions in the Python
|
||||
DB-API specification`_.
|
||||
<psycopg2:tpc>` and the :pep:`optional Two-Phase Commit Extensions in the
|
||||
Python DB-API specification <249#optional-two-phase-commit-extensions>`.
|
||||
|
||||
Callbacks are not run until autocommit is restored on the connection following
|
||||
the commit (because otherwise any queries done in a callback would open an
|
||||
|
@ -387,7 +387,6 @@ autocommit is disabled and you are not within an atomic block will result in an
|
|||
error.
|
||||
|
||||
.. _two-phase commit: https://en.wikipedia.org/wiki/Two-phase_commit_protocol
|
||||
.. _optional Two-Phase Commit Extensions in the Python DB-API specification: https://www.python.org/dev/peps/pep-0249/#optional-two-phase-commit-extensions
|
||||
|
||||
Use in tests
|
||||
------------
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue