1
0
mirror of https://github.com/django/django.git synced 2025-08-08 02:49:26 +00:00

Clarified warning about date-based generic views.

This commit is contained in:
Aymeric Augustin 2012-05-01 11:29:20 +02:00
parent 46b082e05c
commit 80c0cbf1c9

View File

@ -750,9 +750,15 @@ DateMixin
When :doc:`time zone support </topics/i18n/timezones>` is enabled and When :doc:`time zone support </topics/i18n/timezones>` is enabled and
``date_field`` is a ``DateTimeField``, dates are assumed to be in the ``date_field`` is a ``DateTimeField``, dates are assumed to be in the
current time zone. As a consequence, if you have implemented per-user current time zone. Otherwise, the queryset could include objects from
time zone selection, users living in different time zones may view a the previous or the next day in the end user's time zone.
different set of objects at the same URL.
.. warning::
In this situation, if you have implemented per-user time zone
selection, the same URL may show a different set of objects,
depending on the end user's time zone. To avoid this, you should
use a ``DateField`` as the ``date_field`` attribute.
.. attribute:: allow_future .. attribute:: allow_future