#8618: Many-to-many intermediary tables can't have multiple foreign keys to
source/target models
-------------------------------------+--------------------------------------
Reporter: coda | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords: m2m intermediary
validation
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* component: Database wrapper => Core framework
* needs_tests: => 0
* needs_docs: => 0
Comment:
If you read the ticket (#6095) and mailing list discussions surrounding
this feature, this was discussed at the time.
There were a few suggestions on how to do this. Simply removing the check
isn't an option - there is no reason to believe that the first foreign key
will be the correct one.
Two possible options:
1) Convention: the foreign key _without_ a related field is the field for
the M2M relation every time.
2) A new option; something in the Meta class to identify the fields that
should be used for the through.
--
Ticket URL: <http://code.djangoproject.com/ticket/8618#comment:1>
Django Code <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
