From 82a58ce5b67e0b79fa0efbad72e21d9d1be25ceb Mon Sep 17 00:00:00 2001 From: Loic Bistuer Date: Sat, 23 Nov 2013 01:29:09 +0700 Subject: [PATCH] Fixed #21491 -- Removed documented workaround for a known issue. The issue was that two M2M hidden reverse managers (related_name ending with a '+') could clash with each other. Refs #21375 and #15932. Thanks Baptiste. --- docs/ref/models/fields.txt | 7 ------- 1 file changed, 7 deletions(-) diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index f2ae9dfb7e..75f87d4d71 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1230,13 +1230,6 @@ that control how the relationship functions. Same as :attr:`ForeignKey.related_name`. - If you have more than one ``ManyToManyField`` pointing to the same model - and want to suppress the backwards relations, set each ``related_name`` - to a unique value ending with ``'+'``:: - - users = models.ManyToManyField(User, related_name='u+') - referents = models.ManyToManyField(User, related_name='ref+') - .. attribute:: ForeignKey.related_query_name .. versionadded:: 1.6