From 78ba9670af373f5261f95d6560bfd08425adcaad Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Mon, 30 Apr 2012 20:41:38 +0200 Subject: Fixed #18217 -- Time zone support in generic views Introduced a distinct implementation depending on the type of the date field (DateField or DateTimeField), and applied appropriate conversions is the latter case, when time zone support is enabled. --- docs/ref/class-based-views.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs') diff --git a/docs/ref/class-based-views.txt b/docs/ref/class-based-views.txt index aa3f8f7773..5d308694e5 100644 --- a/docs/ref/class-based-views.txt +++ b/docs/ref/class-based-views.txt @@ -748,6 +748,12 @@ DateMixin ``QuerySet``'s model that the date-based archive should use to determine the objects on the page. + When :doc:`time zone support ` is enabled and + ``date_field`` is a ``DateTimeField``, dates are assumed to be in the + current time zone. As a consequence, if you have implemented per-user + time zone selection, users living in different time zones may view a + different set of objects at the same URL. + .. attribute:: allow_future A boolean specifying whether to include "future" objects on this page, -- cgit v1.3