#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__
method
-------------------------------------+-------------------------------------
Reporter: favo <favo@…> | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: SVN
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by jblaine):
I'm interested in ''any'' patch that will give me access to the new data
and operations performed when a model's m2m field is altered. Right now,
m2m_changed is totally useless to me, and is actually '''dangerous''' as
others have pointed out in other bugs related to this one.
Me: ''Remove 2 relationships from these 200 that are set.''
Admin: ''Okay! I removed 200 things and added all 198 items back that did
not match your 2! And I sent not one single pre_remove or post_remove
signal!''
Me: ''That's not at all what I said, and it totally matters how you go
about it and that your signals+actions properly reflect what is being
asked and not reflecting how you went about doing it.''
I suspect it's no surprise that I consider this a bug, not a
"cleanup/optimization" as it's now categorized :(
--
Ticket URL: <https://code.djangoproject.com/ticket/6707#comment:13>
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 [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.
