From 0a28b42b1510b8093a90718bafd7627ed67fa13b Mon Sep 17 00:00:00 2001 From: Hasan Ramezani Date: Wed, 8 Sep 2021 13:57:49 +0200 Subject: Fixed #33084 -- Removed incorrect system check for ManyToManyField with limit_choices_to. --- docs/ref/checks.txt | 2 +- docs/ref/models/fields.txt | 4 ---- 2 files changed, 1 insertion(+), 5 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/checks.txt b/docs/ref/checks.txt index 2ea2fd0df2..c65cb4b6ce 100644 --- a/docs/ref/checks.txt +++ b/docs/ref/checks.txt @@ -310,7 +310,7 @@ Related fields * **fields.W342**: Setting ``unique=True`` on a ``ForeignKey`` has the same effect as using a ``OneToOneField``. * **fields.W343**: ``limit_choices_to`` has no effect on ``ManyToManyField`` - with a ``through`` model. + with a ``through`` model. *This check appeared before Django 4.0.* * **fields.W344**: The field's intermediary table ```` clashes with the table name of ````/``.``. * **fields.W345**: ``related_name`` has no effect on ``ManyToManyField`` with a diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 1a3558ac17..e03b8fa82a 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1810,10 +1810,6 @@ that control how the relationship functions. Same as :attr:`ForeignKey.limit_choices_to`. - ``limit_choices_to`` has no effect when used on a ``ManyToManyField`` with a - custom intermediate table specified using the - :attr:`~ManyToManyField.through` parameter. - .. attribute:: ManyToManyField.symmetrical Only used in the definition of ManyToManyFields on self. Consider the -- cgit v1.3