diff options
| author | Aymeric Augustin <aymeric.augustin@m4x.org> | 2012-04-30 20:41:38 +0200 |
|---|---|---|
| committer | Aymeric Augustin <aymeric.augustin@m4x.org> | 2012-04-30 20:48:19 +0200 |
| commit | 78ba9670af373f5261f95d6560bfd08425adcaad (patch) | |
| tree | fded4e0a6f2c3ab46e1e5367370720fa4c979701 /docs/ref | |
| parent | 596cb9c7e287abbb98c64974fb4944d522cb6b5a (diff) | |
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.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/class-based-views.txt | 6 |
1 files changed, 6 insertions, 0 deletions
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 </topics/i18n/timezones>` 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, |