From eb6c107624930c97390185fdbf7f887c50665808 Mon Sep 17 00:00:00 2001 From: Nick Sandford Date: Fri, 11 Jan 2013 13:57:54 +0800 Subject: Fixed #19360 -- Raised an explicit exception for aggregates on date/time fields in sqlite3 Thanks lsaffre for the report and Chris Medrela for the initial patch. --- docs/ref/models/querysets.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'docs/ref/models') diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 2bbd895fd4..71049703c9 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -2188,6 +2188,14 @@ Django provides the following aggregation functions in the aggregate functions, see :doc:`the topic guide on aggregation `. +.. warning:: + + 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``. + Avg ~~~ -- cgit v1.3