diff options
| author | Aymeric Augustin <aymeric.augustin@m4x.org> | 2019-07-20 18:31:47 +0200 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2019-12-04 18:07:51 +0100 |
| commit | ad88524e4db91dc2f148cf40184a81a454ee7aac (patch) | |
| tree | ec93dc6c92104fa72276cf75d9a6e952716f77cf /docs | |
| parent | a2e96f7969059fb4e621a1cd591fbdd0d4deae2e (diff) | |
Refs #23524 -- Unified BaseDatabaseWrapper.timezone.
There was a special case in this property to return None when the
database backend supports time zone. However, only the PostgreSQL
backend supports time zones and it never uses this property.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/3.1.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/releases/3.1.txt b/docs/releases/3.1.txt index b4179883ab..58f14e172d 100644 --- a/docs/releases/3.1.txt +++ b/docs/releases/3.1.txt @@ -297,6 +297,11 @@ backends. * ``DatabaseOperations.fetch_returned_insert_columns()`` now requires an additional ``returning_params`` argument. +* ``connection.timezone`` property is now ``'UTC'`` by default, or the + :setting:`TIME_ZONE <DATABASE-TIME_ZONE>` when :setting:`USE_TZ` is ``True`` + on databases that support time zones. Previously, it was ``None`` on + databases that support time zones. + Dropped support for MariaDB 10.1 -------------------------------- |