From 9b1cb755a28f020e27d4268c214b25315d4de42e Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Fri, 18 Nov 2011 13:01:06 +0000 Subject: Added support for time zones. Thanks Luke Plant for the review. Fixed #2626. For more information on this project, see this thread: http://groups.google.com/group/django-developers/browse_thread/thread/cf0423bbb85b1bbf git-svn-id: http://code.djangoproject.com/svn/django/trunk@17106 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/models/querysets.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'docs/ref/models') diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 68da9c7343..9736d94838 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -546,6 +546,12 @@ Examples:: >>> Entry.objects.filter(headline__contains='Lennon').dates('pub_date', 'day') [datetime.datetime(2005, 3, 20)] +.. warning:: + + When :doc:`time zone support ` is enabled, Django + uses UTC in the database connection, which means the aggregation is + performed in UTC. This is a known limitation of the current implementation. + none ~~~~ @@ -1953,6 +1959,13 @@ Note this will match any record with a ``pub_date`` that falls on a Monday (day 2 of the week), regardless of the month or year in which it occurs. Week days are indexed with day 1 being Sunday and day 7 being Saturday. +.. warning:: + + When :doc:`time zone support ` is enabled, Django + uses UTC in the database connection, which means the ``year``, ``month``, + ``day`` and ``week_day`` lookups are performed in UTC. This is a known + limitation of the current implementation. + .. fieldlookup:: isnull isnull -- cgit v1.3