mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-22 17:16:24 +00:00
Code Issues 25 Releases Wiki Activity

Fixed #30733 -- Doc'd that datetime lookups require time zone definitions in the database.

Browse Source 
Note was missing for date, year, iso_year, week, time, hour, minute,
and second lookups.
This commit is contained in:
Andrew 2019-08-27 17:37:24 -04:00 committed by Mariusz Felisiak
parent dba749917f
commit 29adcd215f
1 changed files with 20 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/ref/models/querysets.txt
View File

@ -2969,7 +2969,8 @@ Example::
implementation of the relevant query varies among different database engines.)
When :setting:`USE_TZ` is ``True``, fields are converted to the current time
zone before filtering.
zone before filtering. This requires :ref:`time zone definitions in the
database <database-time-zone-definitions>`.
.. fieldlookup:: year
@ -2994,7 +2995,8 @@ SQL equivalent:
(The exact SQL syntax varies for each database engine.)
When :setting:`USE_TZ` is ``True``, datetime fields are converted to the
current time zone before filtering.
current time zone before filtering. This requires :ref:`time zone definitions
in the database <database-time-zone-definitions>`.
.. fieldlookup:: iso_year
@ -3014,7 +3016,8 @@ Example::
(The exact SQL syntax varies for each database engine.)
When :setting:`USE_TZ` is ``True``, datetime fields are converted to the
current time zone before filtering.
current time zone before filtering. This requires :ref:`time zone definitions
in the database <database-time-zone-definitions>`.
.. fieldlookup:: month
@ -3088,8 +3091,9 @@ Example::
(No equivalent SQL code fragment is included for this lookup because
implementation of the relevant query varies among different database engines.)
When :setting:`USE_TZ` is ``True``, fields are converted to the current time
zone before filtering.
When :setting:`USE_TZ` is ``True``, datetime fields are converted to the
current time zone before filtering. This requires :ref:`time zone definitions
in the database <database-time-zone-definitions>`.
.. fieldlookup:: week_day
@ -3155,7 +3159,8 @@ Example::
implementation of the relevant query varies among different database engines.)
When :setting:`USE_TZ` is ``True``, fields are converted to the current time
zone before filtering.
zone before filtering. This requires :ref:`time zone definitions in the
database <database-time-zone-definitions>`.
.. fieldlookup:: hour
@ -3181,8 +3186,9 @@ SQL equivalent:
(The exact SQL syntax varies for each database engine.)
For datetime fields, when :setting:`USE_TZ` is ``True``, values are converted
to the current time zone before filtering.
When :setting:`USE_TZ` is ``True``, datetime fields are converted to the
current time zone before filtering. This requires :ref:`time zone definitions
in the database <database-time-zone-definitions>`.
.. fieldlookup:: minute
@ -3208,8 +3214,9 @@ SQL equivalent:
(The exact SQL syntax varies for each database engine.)
For datetime fields, When :setting:`USE_TZ` is ``True``, values are converted
to the current time zone before filtering.
When :setting:`USE_TZ` is ``True``, datetime fields are converted to the
current time zone before filtering. This requires :ref:`time zone definitions
in the database <database-time-zone-definitions>`.
.. fieldlookup:: second
@ -3235,8 +3242,9 @@ SQL equivalent:
(The exact SQL syntax varies for each database engine.)
For datetime fields, when :setting:`USE_TZ` is ``True``, values are converted
to the current time zone before filtering.
When :setting:`USE_TZ` is ``True``, datetime fields are converted to the
current time zone before filtering. This requires :ref:`time zone definitions
in the database <database-time-zone-definitions>`.
.. fieldlookup:: isnull