From 9451d8d558e6dafa4e270c33608a291610ccf77d Mon Sep 17 00:00:00 2001 From: Matt Austin Date: Thu, 12 Sep 2013 21:27:35 +0800 Subject: [PATCH] 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 ++++++--- docs/releases/1.6.txt | 15 +++++++++++++++ 2 files changed, 21 insertions(+), 3 deletions(-) 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 diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt index 27c7482535..a7448e0da1 100644 --- a/docs/releases/1.6.txt +++ b/docs/releases/1.6.txt @@ -435,6 +435,21 @@ but will not be removed from Django until version 1.8. .. _recommendations in the Python documentation: http://docs.python.org/2/library/doctest.html#unittest-api +Time zone-aware ``day``, ``month``, and ``week_day`` lookups +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Django 1.6 introduces time zone support for :lookup:`day`, :lookup:`month`, +and :lookup:`week_day` lookups when :setting:`USE_TZ` is ``True``. These +lookups were previously performed in UTC regardless of the current time zone. + +This requires :ref:`time zone definitions in the database +`. If you're using SQLite, you must install +pytz_. If you're using MySQL, you must install pytz_ and load the time zone +tables with `mysql_tzinfo_to_sql`_. + +.. _pytz: http://pytz.sourceforge.net/ +.. _mysql_tzinfo_to_sql: http://dev.mysql.com/doc/refman/5.5/en/mysql-tzinfo-to-sql.html + Addition of ``QuerySet.datetimes()`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~