mirror of
https://github.com/django/django.git
synced 2025-08-03 18:38:50 +00:00
Refs #14357 -- Made Meta.ordering not affect GROUP BY queries.
Per deprecation timeline.
This commit is contained in:
parent
d17be88afd
commit
0ddb4ebf7b
7 changed files with 7 additions and 54 deletions
|
@ -512,13 +512,6 @@ include the aggregate column.
|
|||
Interaction with default ordering or ``order_by()``
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. deprecated:: 2.2
|
||||
|
||||
Starting in Django 3.1, the ordering from a model's ``Meta.ordering`` won't
|
||||
be used in ``GROUP BY`` queries, such as ``.annotate().values()``. Since
|
||||
Django 2.2, these queries issue a deprecation warning indicating to add an
|
||||
explicit ``order_by()`` to the queryset to silence the warning.
|
||||
|
||||
Fields that are mentioned in the ``order_by()`` part of a queryset (or which
|
||||
are used in the default ordering on a model) are used when selecting the
|
||||
output data, even if they are not otherwise specified in the ``values()``
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue