mirror of
https://github.com/django/django.git
synced 2025-08-02 18:13:02 +00:00
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.
This commit is contained in:
parent
596cb9c7e2
commit
78ba9670af
6 changed files with 239 additions and 51 deletions
|
@ -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,
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue