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
..
base	Fixed #23820 -- Supported per-database time zone.	2015-05-17 09:40:28 +02:00
dummy	Fixed #24394 -- Allowed running tests with empty default dictionary.	2015-03-25 17:56:59 -04:00
mysql	Fixed #23820 -- Supported per-database time zone.	2015-05-17 09:40:28 +02:00
oracle	Fixed #23820 -- Supported per-database time zone.	2015-05-17 09:40:28 +02:00
postgresql_psycopg2	Fixed #23820 -- Supported per-database time zone.	2015-05-17 09:40:28 +02:00
sqlite3	Fixed #23820 -- Supported per-database time zone.	2015-05-17 09:40:28 +02:00
__init__.py	Fixed #22603 -- Reorganized classes in django.db.backends.	2015-01-14 14:16:20 -05:00
signals.py	Fixed #13798 -- Added connection argument to the connection_created signal. Thanks to liangent for the report, and Alex Gaynor for the patch.	2010-08-30 13:21:18 +00:00
utils.py	Sorted imports with isort; refs #23860.	2015-02-06 08:16:28 -05:00