#30355: Specifying custom manager doesn't work with prefetch
-------------------------------------+-------------------------------------
     Reporter:  Kyle Mulka           |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.11
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Daniel Hepper):

 * stage:  Unreviewed => Accepted


Comment:

 I was about to write a patch for the docs on "Using a custom reverse
 manager" to highlight the implication of using prefetch with custom
 managers.

 But thinking about it further made me realize that the prefetch might have
 happened in a completely unrelated part of the code. As a conclusion, I'd
 consider this a bug.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30355#comment:2>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.3e577da4c10b62c226afe52819ba7f55%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to