From 709ee83cd3ccbaeabcfcbb9391bb72d1bcaf01d3 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 11 Apr 2013 14:13:09 -0400 Subject: [PATCH] [1.5.x] Fixed #20243 - Clarified when RelatedManager.remove() exists. Backport of 712a792713 from master --- docs/ref/models/relations.txt | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/docs/ref/models/relations.txt b/docs/ref/models/relations.txt index 37986ec08d1..c923961a194 100644 --- a/docs/ref/models/relations.txt +++ b/docs/ref/models/relations.txt @@ -82,14 +82,13 @@ Related objects reference >>> e = Entry.objects.get(id=234) >>> b.entry_set.remove(e) # Disassociates Entry e from Blog b. - In order to prevent database inconsistency, this method only exists on - :class:`~django.db.models.ForeignKey` objects where ``null=True``. If - the related field can't be set to ``None`` (``NULL``), then an object - can't be removed from a relation without being added to another. In the - above example, removing ``e`` from ``b.entry_set()`` is equivalent to - doing ``e.blog = None``, and because the ``blog`` - :class:`~django.db.models.ForeignKey` doesn't have ``null=True``, this - is invalid. + For :class:`~django.db.models.ForeignKey` objects, this method only + exists if ``null=True``. If the related field can't be set to ``None`` + (``NULL``), then an object can't be removed from a relation without + being added to another. In the above example, removing ``e`` from + ``b.entry_set()`` is equivalent to doing ``e.blog = None``, and because + the ``blog`` :class:`~django.db.models.ForeignKey` doesn't have + ``null=True``, this is invalid. .. method:: clear()