mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-09-26 12:09:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

[1.6.x] Fixed #21095 -- Documented new requirement for dates lookups.

Browse source 
Day, month, and week_day lookups now require time zone definitions in the database.

Backport of 9451d8d from master.
This commit is contained in:
Matt Austin 2013-09-12 21:27:35 +08:00 • committed by Aymeric Augustin
parent 66e6e2d146
commit a929adfd3b
2 changed files with 21 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/ref/models/querysets.txt
View file

@ -2232,7 +2232,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 <database-time-zone-definitions>`.
.. fieldlookup:: day
@ -2255,7 +2256,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 <database-time-zone-definitions>`.
.. fieldlookup:: week_day
@ -2279,7 +2281,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 <database-time-zone-definitions>`.
.. fieldlookup:: hour