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

Fixed #17461 -- Doc'd the presumed order of foreign keys on the intermediary model of a self-referential m2m.

Browse Source 
Thanks Giannis Terzopoulos and Sarah Boyce for the reviews.
This commit is contained in:
Clifford Gama
2024-11-03 16:32:55 +02:00
committed by Sarah Boyce
parent 0f5dd0dff3
commit 9d93e35c20
2 changed files with 42 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/topics/db/models.txt
View File

@@ -533,9 +533,12 @@ There are a few restrictions on the intermediate model:
* For a model which has a many-to-many relationship to itself through an
intermediary model, two foreign keys to the same model are permitted, but
they will be treated as the two (different) sides of the many-to-many
relationship. If there are *more* than two foreign keys though, you
must also specify ``through_fields`` as above, or a validation error
will be raised.
relationship. If :attr:`~.ManyToManyField.through_fields` is not specified,
the first foreign key will be taken to represent the source side of the
``ManyToManyField``, while the second will be taken to represent the target
side. If there are *more* than two foreign keys though, you must specify
:attr:`~.ManyToManyField.through_fields` to explicitly indicate which foreign
keys to use, otherwise a validation error will be raised.
Now that you have set up your :class:`~django.db.models.ManyToManyField` to use
your intermediary model (``Membership``, in this case), you're ready to start