#17461: Document presumed order of foreign keys on intermediate M2M model
--------------------------------------+------------------------------------
Reporter: flytwokites@… | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.3
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by gabrielhurley):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 1
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
This is true specifically for asymmetric M2M's using an intermediate
model; it's an implementation detail coded into the accessor calls here:
https://code.djangoproject.com/browser/django/trunk/django/db/models/fields/related.py#L1135
and a little lower down, here:
https://code.djangoproject.com/browser/django/trunk/django/db/models/fields/related.py#L1154
It's worth noting that this the case in the docs, probably under the
"symmetrical" section of the docs here:
https://docs.djangoproject.com/en/1.3/ref/models/fields/#django.db.models.ManyToManyField.symmetrical
--
Ticket URL: <https://code.djangoproject.com/ticket/17461#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
