mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-24 14:16:09 +00:00
Code Issues 32 Releases Wiki Activity

Fixed #33084 -- Removed incorrect system check for ManyToManyField with limit_choices_to.

Browse Source
This commit is contained in:
Hasan Ramezani
2021-09-08 13:57:49 +02:00
committed by Mariusz Felisiak
parent 46c8df640c
commit 0a28b42b15
6 changed files with 34 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/checks.txt
View File

@@ -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 ``<table name>`` clashes with
the table name of ``<model>``/``<model>.<field name>``.
* **fields.W345**: ``related_name`` has no effect on ``ManyToManyField`` with a

4
docs/ref/models/fields.txt
View File

@@ -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