#36686: Clarify the behavior difference between order_by() and Meta.ordering in
GROUP BY queries
-------------------------------------+-------------------------------------
     Reporter:  Wouter               |                    Owner:  (none)
         Type:  Bug                  |                   Status:  new
    Component:  Documentation        |                  Version:  5.2
     Severity:  Normal               |               Resolution:
     Keywords:  aggregate,           |             Triage Stage:  Accepted
  order_by, ordering                 |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):

 I just happened to bump into this
 
[https://docs.djangoproject.com/en/5.2/ref/models/querysets/#:~:text=default%20model
 additional language]:

 > Similarly, if you use a values() query to restrict the columns selected,
 the columns used in any order_by() (or default model ordering) will still
 be involved and may affect uniqueness of the results.

 Might want to clarify that one also?
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36686#comment:3>
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 visit 
https://groups.google.com/d/msgid/django-updates/0107019a181d4685-00311c87-9f7c-400d-9ce8-63bff1b12ae4-000000%40eu-central-1.amazonses.com.

Reply via email to