#30771: Filtering on query result overrides GROUP BY of internal query
-------------------------------------+-------------------------------------
     Reporter:  Aur Saraf            |                    Owner:  James
                                     |  Timmins
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  annotate,            |             Triage Stage:  Accepted
  annotation, filter, groupby,       |
  aggregate, aggregation             |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"0719edcd5fed56157ffb3323a8f634aa5e8f9a80" 0719edc]:
 {{{
 #!CommitTicketReference repository=""
 revision="0719edcd5fed56157ffb3323a8f634aa5e8f9a80"
 Fixed #30771 -- Fixed exact lookup against queries with selected columns.

 Use pre-existing select fields (and thereby GROUP BY fields) from
 subquery if they were specified, instead of always defaulting to pk.

 Thanks Aur Saraf for the report and Simon Charette for guidance.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30771#comment:11>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.6224211f2b4e6e360739e63cd3980f8a%40djangoproject.com.

Reply via email to