diff options
| author | Nick Pope <nick.pope@flightdataservices.com> | 2020-04-30 10:30:11 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2020-05-13 09:38:40 +0200 |
| commit | 15d76dc2abefc799ecbc3545ae90aefe765d4144 (patch) | |
| tree | 79791c8d35b42625894f5085f049e610418cad3b /docs/topics | |
| parent | d6e6695d9352720fd626b3a6e7f8c836d5da346e (diff) | |
[3.1.x] Used :pep: role in various docs.
Backport of a9337b4add01e50ed8ff8d3ef44099a08cba475c from master
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/db/transactions.txt | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index 40a36e777d..44a21e5ee2 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -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 ------------ |