Corrected exception types in QuerySet docs.
This commit is contained in:
parent
12d6cae7c0
commit
9a0e5052ed
|
@ -644,7 +644,7 @@ A few subtleties that are worth mentioning:
|
||||||
ignored.
|
ignored.
|
||||||
|
|
||||||
* Calling :meth:`only()` and :meth:`defer()` after ``values()`` doesn't make
|
* 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`
|
* Combining transforms and aggregates requires the use of two :meth:`annotate`
|
||||||
calls, either explicitly or as keyword arguments to :meth:`values`. As above,
|
calls, either explicitly or as keyword arguments to :meth:`values`. As above,
|
||||||
|
@ -3491,8 +3491,7 @@ documentation to learn how to create your aggregates.
|
||||||
SQLite can't handle aggregation on date/time fields out of the box.
|
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
|
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
|
currently emulates these features using a text field. Attempts to use
|
||||||
aggregation on date/time fields in SQLite will raise
|
aggregation on date/time fields in SQLite will raise ``NotSupportedError``.
|
||||||
``NotImplementedError``.
|
|
||||||
|
|
||||||
.. admonition:: Note
|
.. admonition:: Note
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue