diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-07-21 12:54:38 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-07-21 12:54:38 +0200 |
| commit | 02376f1f53db24039c200ef4818d96accf16a88b (patch) | |
| tree | e761e9f83d5f2d0088a26525e34596dc5c593a17 /docs | |
| parent | e4a5527d1dc2f8183883931560f3a6dcdef0ab0c (diff) | |
Added missing backticks in docs.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/models/options.txt | 2 | ||||
| -rw-r--r-- | docs/releases/1.8.2.txt | 5 | ||||
| -rw-r--r-- | docs/topics/db/transactions.txt | 2 |
3 files changed, 5 insertions, 4 deletions
diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt index 06bf09fba0..6f318b2df8 100644 --- a/docs/ref/models/options.txt +++ b/docs/ref/models/options.txt @@ -445,7 +445,7 @@ not be looking at your Django code. For example:: unique_together = ["driver", "restaurant"] A :class:`~django.db.models.ManyToManyField` cannot be included in - unique_together. (It's not clear what that would even mean!) If you + ``unique_together``. (It's not clear what that would even mean!) If you need to validate uniqueness related to a :class:`~django.db.models.ManyToManyField`, try using a signal or an explicit :attr:`through <ManyToManyField.through>` model. diff --git a/docs/releases/1.8.2.txt b/docs/releases/1.8.2.txt index 4e03a0e1de..db1f8bf909 100644 --- a/docs/releases/1.8.2.txt +++ b/docs/releases/1.8.2.txt @@ -48,8 +48,9 @@ Bugfixes * Fixed ``isnull`` lookup for ``HStoreField`` (:ticket:`24751`). -* Fixed a MySQL crash when a migration removes a combined index (unique_together - or index_together) containing a foreign key (:ticket:`24757`). +* Fixed a MySQL crash when a migration removes a combined index ( + ``unique_together`` or ``index_together``) containing a foreign key + (:ticket:`24757`). * Fixed session cookie deletion when using :setting:`SESSION_COOKIE_DOMAIN` (:ticket:`24799`). diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index d3b70b3883..c43312ec0f 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -661,7 +661,7 @@ will fail with the error "current transaction is aborted, queries ignored until end of transaction block". While the basic use of ``save()`` is unlikely to raise an exception in PostgreSQL, there are more advanced usage patterns which might, such as saving objects with unique fields, saving using the -force_insert/force_update flag, or invoking custom SQL. +``force_insert``/``force_update`` flag, or invoking custom SQL. There are several ways to recover from this sort of error. |