#14649: .save_m2m() will override any Many-to-Many relationships created via
signals/save method overloading.
------------------------------------+---------------------------------------
Reporter: chrischambers | Owner: nobody
Status: closed | Milestone:
Component: Forms | Version: 1.2
Resolution: wontfix | Keywords: save_m2m, signals,
post_save, save_method
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not sure I agree it's counterintuitive, because I can't see what
*would* be intuitive in this case. The sequence of model saving and inline
saving is inherently complicated, and I don't see how we could easily
maintain the user-space code structure you have described *and* satisfy
the basic saving requirements of m2m form elements.
Even if it is counterintuitive, this ticket doesn't contain a proposal for
what *would* be an intuitive interface.
Closing wontfix; Looking at the example, #2750 would appear to be a better
way to address this use case.
--
Ticket URL: <http://code.djangoproject.com/ticket/14649#comment:1>
Django <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.
