#17: Metasystem optimization: Share select_related in memory
----------------------+-----------------------------------------------------
   Reporter:  adrian  |                Owner:  nobody          
     Status:  new     |            Component:  Database wrapper
    Version:          |           Resolution:                  
   Keywords:          |                Stage:  Accepted        
  Has_patch:  1       |           Needs_docs:  1               
Needs_tests:  0       |   Needs_better_patch:  1               
----------------------+-----------------------------------------------------
Changes (by jacob):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted
  * needs_docs:  0 => 1

Comment:

 This is a ''very'' good idea, but isn't quite ready for prime-time. Some
 things that need fixing:
 
  * The class attribute feels hackish, and is badly named. I'd prefer
 something simpler like {{{Model.objects.select_related(cache=False)}}} --
 any reason not to do this?
  * A note needs to be added to the docs about this behavior so that people
 don't get bitten by stale select related stuff.
  * There's a lot of dense code here without docstrings/comments; I can
 barely follow what's going on. Some more explanation of what's happening
 would be very nice with a feature of this complexity.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/17#comment:18>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to