#12337: save_m2m() does not honor save_instance's exclude argument
-------------------------------------+--------------------------------------
Reporter: margieroginski | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: 1.1
Resolution: invalid | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by margieroginski):
Are you sure it even works to specify an m2m field in the exclude list?
Since exclude is not even used in save_m2m, it seems it would not honor
exclude even if specified statically.
In any case, I don't see why you wouldn't want to honor exclude on an m2m
field when specified dynamically as I described in my example above. It
seems like very inconsistent behavior to not honor exclude for an m2m
field and it seems that a simple and backward compatible fix like the one
I suggested to could be added to solve the problem.
I don't agree this should be closed, I hope you will reconsider it.
Thanks,
Margie
--
Ticket URL: <http://code.djangoproject.com/ticket/12337#comment:2>
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 django-upda...@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.
