summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorcan <cansarigol@derinbilgi.com.tr>2019-06-12 16:35:06 +0300
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2019-06-13 09:29:43 +0200
commitfde9b7d35e4e185903cc14aa587ca870037941b1 (patch)
tree6f55b844bc14561603e73e9185bc987466e57cac /docs
parent3dca8738cbbbb5674f795169e5ea25e2002f2d71 (diff)
Fixed #30128 -- Fixed handling timedelta timezone in database functions.
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/3.0.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/releases/3.0.txt b/docs/releases/3.0.txt
index e58a18f9da..80c1d8904b 100644
--- a/docs/releases/3.0.txt
+++ b/docs/releases/3.0.txt
@@ -315,6 +315,13 @@ backends.
``can_return_ids_from_bulk_insert`` are renamed to
``can_return_columns_from_insert`` and ``can_return_rows_from_bulk_insert``.
+* Database functions now handle :class:`datetime.timezone` formats when created
+ using :class:`datetime.timedelta` instances (e.g.
+ ``timezone(timedelta(hours=5))``, which would output ``'UTC+05:00'``).
+ Third-party backends should handle this format when preparing
+ :class:`~django.db.models.DateTimeField` in ``datetime_cast_date_sql()``,
+ ``datetime_extract_sql()``, etc.
+
:mod:`django.contrib.gis`
-------------------------