1
0
mirror of https://github.com/django/django.git synced 2025-10-09 14:59:24 +00:00

[6.0.x] Added missing backticks in docs/ref/models/fields.txt.

Backport of 4a8ca8bd6906b705c4445bc915d71beda2fc4b84 from main
This commit is contained in:
Mariusz Felisiak 2025-10-08 10:58:59 +02:00
parent ec81e68000
commit 934c55f1f9

View File

@ -1730,8 +1730,9 @@ The possible values for :attr:`~ForeignKey.on_delete` are found in
* .. attribute:: CASCADE * .. attribute:: CASCADE
Cascade deletes. Django emulates the behavior of the SQL constraint ON Cascade deletes. Django emulates the behavior of the SQL constraint ``ON
DELETE CASCADE and also deletes the object containing the ForeignKey. DELETE CASCADE`` and also deletes the object containing the
:class:`ForeignKey`.
:meth:`.Model.delete` isn't called on related models, but the :meth:`.Model.delete` isn't called on related models, but the
:data:`~django.db.models.signals.pre_delete` and :data:`~django.db.models.signals.pre_delete` and
@ -1950,9 +1951,9 @@ The possible values for :attr:`~ForeignKey.on_delete` are found in
Setting it to ``False`` does not mean you can reference a swappable model Setting it to ``False`` does not mean you can reference a swappable model
even if it is swapped out - ``False`` means that the migrations made even if it is swapped out - ``False`` means that the migrations made
with this ForeignKey will always reference the exact model you specify with this :class:`ForeignKey` will always reference the exact model you
(so it will fail hard if the user tries to run with a User model you don't specify (so it will fail hard if the user tries to run with a ``User``
support, for example). model you don't support, for example).
If in doubt, leave it to its default of ``True``. If in doubt, leave it to its default of ``True``.