id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
30638	Allow the per-database TIME_ZONE option on databases that support timezones.	Aymeric Augustin	Aymeric Augustin	"I have a Django project that connects to a third-party PostgreSQL database (actually, Redshift, but that's the same as PostgreSQL for the purpose of this ticket).

I do not control the scheme of that database. It uses `timestamp` (timezone naive) values in UTC for datetimes rather than `timestamp with time zone` (timezone aware).

Django reads naive datetimes in UTC from this database and assumes they're in Europe/Paris (my global TIME_ZONE setting) so they're off by 2 hours in the admin.

I would like to set the `TIME_ZONE` option for this database connection to `UTC` in order to read and write naive datetimes in UTC rather than Europe/Paris.

Unfortunately:

> When USE_TZ is True and the database supports time zones (e.g. PostgreSQL), it is an error to set this option.

I think it should be allowed."	New feature	closed	Database layer (models, ORM)	dev	Normal	wontfix			Accepted	0	0	0	0	0	0