1
0
mirror of https://github.com/django/django.git synced 2025-10-26 15:16:09 +00:00

Fixed #36530 -- Extended fields.E347 to check for ManyToManyField involving CompositePrimaryKey on either side.

Thanks to Jacob Walls for the report.
This commit is contained in:
jkhall81
2025-07-28 08:59:07 -07:00
committed by nessita
parent e664c5afa9
commit 2013092b69
4 changed files with 68 additions and 53 deletions

View File

@@ -338,8 +338,8 @@ Related fields
* **fields.W345**: ``related_name`` has no effect on ``ManyToManyField`` with a
symmetrical relationship, e.g. to "self".
* **fields.W346**: ``db_comment`` has no effect on ``ManyToManyField``.
* **fields.E347**: Field defines a relation to the ``CompositePrimaryKey`` of
model ``<model>`` which is not supported.
* **fields.E347**: Field defines a relation involving model ``<model>`` which
has a ``CompositePrimaryKey`` and such relations are not supported.
* **fields.E348**: Related name ``<related_name>`` for ``<model>.<field name>``
clashes with the name of a model manager.

View File

@@ -21,3 +21,7 @@ Bugfixes
(:ticket:`36518`).
* Added compatibility for ``docutils`` 0.22 (:ticket:`36535`).
* Fixed a crash in Django 5.2 when using a ``ManyToManyField`` on a model with
a composite primary key, by extending the ``fields.E347`` system check
(:ticket:`36530`).