From 462d7837f93c02f0812368737294c9fde997229f Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Sat, 12 Sep 2020 21:49:28 +0200 Subject: [PATCH] [3.1.x] Corrected exception types in QuerySet docs. Backport of 9a0e5052ed5509cc582b1b3eeaa30f85858fee48 from master --- docs/ref/models/querysets.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 8c63a8aa5a2..1b3f703bdf4 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -594,7 +594,7 @@ A few subtleties that are worth mentioning: ignored. * Calling :meth:`only()` and :meth:`defer()` after ``values()`` doesn't make - sense, so doing so will raise a ``NotImplementedError``. + sense, so doing so will raise a ``TypeError``. * Combining transforms and aggregates requires the use of two :meth:`annotate` calls, either explicitly or as keyword arguments to :meth:`values`. As above, @@ -3406,8 +3406,7 @@ documentation to learn how to create your aggregates. SQLite can't handle aggregation on date/time fields out of the box. This is because there are no native date/time fields in SQLite and Django currently emulates these features using a text field. Attempts to use - aggregation on date/time fields in SQLite will raise - ``NotImplementedError``. + aggregation on date/time fields in SQLite will raise ``NotSupportedError``. .. admonition:: Note