From 9451d8d558e6dafa4e270c33608a291610ccf77d Mon Sep 17 00:00:00 2001 From: Matt Austin Date: Thu, 12 Sep 2013 21:27:35 +0800 Subject: Fixed #21095 -- Documented new requirement for dates lookups. Day, month, and week_day lookups now require time zone definitions in the database. --- docs/ref/models/querysets.txt | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index c62525cb72..bb9f303571 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -2274,7 +2274,8 @@ SQL equivalent:: (The exact SQL syntax varies for each database engine.) When :setting:`USE_TZ` is ``True``, datetime fields are converted to the -current time zone before filtering. +current time zone before filtering. This requires :ref:`time zone definitions +in the database `. .. fieldlookup:: day @@ -2297,7 +2298,8 @@ Note this will match any record with a pub_date on the third day of the month, such as January 3, July 3, etc. When :setting:`USE_TZ` is ``True``, datetime fields are converted to the -current time zone before filtering. +current time zone before filtering. This requires :ref:`time zone definitions +in the database `. .. fieldlookup:: week_day @@ -2321,7 +2323,8 @@ Note this will match any record with a ``pub_date`` that falls on a Monday (day are indexed with day 1 being Sunday and day 7 being Saturday. When :setting:`USE_TZ` is ``True``, datetime fields are converted to the -current time zone before filtering. +current time zone before filtering. This requires :ref:`time zone definitions +in the database `. .. fieldlookup:: hour -- cgit v1.3