#5390: Add signals to ManyRelatedManager
----------------------------------------------------------+-----------------
Reporter: Ludovico Magnocavallo <l...@qix.it> | Owner:
rvdrijst
Status: assigned | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
manytomanyfield feature signals
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
----------------------------------------------------------+-----------------
Comment (by russellm):
@frans - No - the m2m refactor doesn't solve #5390. The signals are at a
different granularity. The proposal for this ticket is to send a 'change'
signal whenever the m2m field is changed; if you allow signals on the m2m
intermediate, you get a signal for each and every object you assign. So -
{{{
author.books = [1,2,3,4]
}}}
Would generate 4 signals if you listened to the intermediate model, but 1
based on the proposal from this ticket.
It is for this reason that save and delete signals on auto-generated m2m
models are explicitly disabled.
--
Ticket URL: <http://code.djangoproject.com/ticket/5390#comment:45>
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.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=.
