#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__
method
--------------------------------------+-------------------------------------
Reporter: favo <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Design decision
needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------+-------------------------------------
Comment (by favo <[EMAIL PROTECTED]>):
Yes, as you said, it's depends. And it's true the patch need a extra full
database query. However when you use it in some m2m widget like the admin
ones, you already do a full database query to show all choices. And the
patch don't change the exist data(don't like before remove but add
later.), this make sense in some situation. In one of my project, we have
lot's signal hook with m2m relationship changed(with the help of #5390),
each receiver have to run a heavy database logic, so we need this patch do
reduce unnecessary changes.
Anyway it's a balance, not a universal improvement, I write here, but part
people need it.
mtredinnick, thanks for feedback. But I didn't find the ticket you
mentioned?
--
Ticket URL: <http://code.djangoproject.com/ticket/6707#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
