Don't Set TIME_ZONE unless it is explictly needed (or put it back to how you found it)
|Reported by:||Owned by:||jedie|
|Cc:||philz42, Ramiro Morales, Thomas Schreiber, jedie, bas@…, Gabriel Hurley||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
my understanding is that postgres needs the TIME_ZONE setting in order to work properly, and hence why it is in the settings.py file.
I just got bit by a nasty buy which was due to django setting/changing the timezone and then not setting it back to what it was after it was done. causing some pages to display CST and others to show PST (depending on weather the apache process had run a django request or not)
Is there a way django can either:
a) not set the time_zone expliclty and just use whatever the system says?
b) reset it back to what it was when it finishes up the request
Change History (23)
comment:18 Changed 7 years ago by
|Owner:||changed from Ramiro Morales to jedie|
|Status:||new → assigned|