diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2019-09-07 19:28:19 +0200 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2019-09-10 12:01:00 +0200 |
| commit | 0ddb4ebf7bfcc4730c80a772dd146a49ef6895f6 (patch) | |
| tree | c6a203b757d104c08c4a9786ac1521b87c26fe0a /docs/topics | |
| parent | d17be88afd5f5e1059491e10408ba239e2e99fe2 (diff) | |
Refs #14357 -- Made Meta.ordering not affect GROUP BY queries.
Per deprecation timeline.
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/db/aggregation.txt | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/docs/topics/db/aggregation.txt b/docs/topics/db/aggregation.txt index 6e5c6271dd..0a64c703dc 100644 --- a/docs/topics/db/aggregation.txt +++ b/docs/topics/db/aggregation.txt @@ -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()`` |