mirror of
https://github.com/django/django.git
synced 2025-06-05 19:49:13 +00:00
ticket #34699. fixed documentation spel chek error. Reformatted example to be inside warning block.
This commit is contained in:
parent
99446762fc
commit
a603dbabea
@ -660,15 +660,13 @@ Usage example:
|
||||
|
||||
.. warning::
|
||||
|
||||
Trunc functions, at the database level, return a timezone naive value which
|
||||
is converted to a timezone aware value by the ORM. When you use a Trunc
|
||||
function in a filter you will need to remember that it is a timezone naive
|
||||
value. This can lead to unexpected results if you are using timezones other
|
||||
than UTC. Django will store date/time values in the database in the UTC
|
||||
timezone. The following example demonstrates what happens when using the
|
||||
timezone "Europe/Berlin" and how to adjust for this:
|
||||
|
||||
Filter example using the "Europe/Berlin" timezone.:
|
||||
``Trunc`` functions, at the database level, return a timezone naive value
|
||||
which is converted to a timezone aware value by the ORM. When you use a
|
||||
``Trunc`` function in a filter you will need to remember that it is a
|
||||
timezone naive value. This can lead to unexpected results if you are using
|
||||
timezones other than UTC. Django will store date/time values in the
|
||||
database in the UTC timezone. The following example demonstrates what
|
||||
happens when using the timezone "Europe/Berlin" and how to adjust for this:
|
||||
|
||||
.. code-block:: pycon
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user