#25403: Subqueries: a common case where people get tempted to use .extra()
-------------------------------------+-------------------------------------
     Reporter:  PaoloC68             |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  QuerySet.extra       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by PaoloC68):

 Replying to [comment:7 timgraham]:
 Tim don't you think that the [comment:4 akaariai] example resembles  in a
 cleaner way the two proposals that you mentioned?
 I mean, you are right, in someway overlaps but the way he exposed seems
 making more sense an aligned to whole system.

--
Ticket URL: <https://code.djangoproject.com/ticket/25403#comment:8>
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/066.5c6ba03f6b9b7240dbb07046f1e3f929%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to