diff options
author | Matt Austin <mail@mattaustin.me.uk> | 2013-09-12 21:27:35 +0800 |
---|---|---|
committer | Aymeric Augustin <aymeric.augustin@m4x.org> | 2013-09-13 10:20:13 +0200 |
commit | a929adfd3b89056d83c34f729bedde78afec44db (patch) | |
tree | 5165d85f84d43552058f957092ea8e7cd1a09c95 | |
parent | 66e6e2d14663f78aacdd9df4e9e8c1c008b62459 (diff) | |
download | django-a929adfd3b89056d83c34f729bedde78afec44db.tar.gz |
[1.6.x] Fixed #21095 -- Documented new requirement for dates lookups.
Day, month, and week_day lookups now require time zone definitions in the database.
Backport of 9451d8d from master.
-rw-r--r-- | docs/ref/models/querysets.txt | 9 | ||||
-rw-r--r-- | 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 138c8439f6..4fdea9b939 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -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 diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt index f5a2595efa..7e0e5a5e54 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 +<database-time-zone-definitions>`. 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()`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |