#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
--------------------------------------+-------------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
This change runs a whole extra database query, which is far from zero
cost. So each approach is better in different circumstances and there's no
way to tell which one will be better ahead of time. Thus a change like
this would just be changing things, not a universal improvement.
A better approach would be to track what's changed by tracking the old
values before updating them, which has been suggested in another ticket.
I'm not convinced that's a good idea for all fields, but it might be
worthwhile for the multi-valued relations like many-to-many.
--
Ticket URL: <http://code.djangoproject.com/ticket/6707#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
