Aymeric Augustin
ed83881e64
Fixed #23820 -- Supported per-database time zone.
...
The primary use case is to interact with a third-party database (not
primarily managed by Django) that doesn't support time zones and where
datetimes are stored in local time when USE_TZ is True.
Configuring a PostgreSQL database with the TIME_ZONE option while USE_TZ
is False used to result in silent data corruption. Now this is an error.
2015-05-17 09:40:28 +02:00
..
2015-02-22 09:35:39 -05:00
2015-05-01 13:26:42 -04:00
2015-05-01 13:26:42 -04:00
2015-05-01 13:26:42 -04:00
2015-02-20 09:21:39 -05:00
2015-01-19 11:12:57 -05:00
2015-02-20 09:21:39 -05:00
2015-01-02 19:20:18 -05:00
2015-02-20 09:21:39 -05:00
2015-01-27 11:48:04 -05:00
2015-03-18 19:20:07 -04:00
2015-02-15 20:47:04 +01:00
2015-02-20 09:21:39 -05:00
2015-01-19 11:12:57 -05:00
2015-02-20 09:21:39 -05:00
2015-05-08 13:05:50 -04:00
2015-01-19 11:12:57 -05:00
2015-02-20 09:21:39 -05:00
2015-02-20 09:21:39 -05:00
2015-03-18 19:20:07 -04:00
2015-05-08 13:05:50 -04:00
2015-02-20 09:21:39 -05:00
2015-01-27 11:48:04 -05:00
2015-02-25 08:47:11 -05:00
2015-03-09 10:12:21 -04:00
2015-04-14 22:11:40 -04:00
2015-05-01 16:24:39 -04:00
2015-05-01 13:26:42 -04:00
2015-05-13 10:11:05 -04:00
2015-05-15 18:44:20 +02:00
2015-05-07 08:52:06 -04:00
2015-05-17 09:40:28 +02:00
2015-05-01 16:52:19 -04:00
2015-03-18 20:36:50 -04:00