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 2626 Datetime handling is broken when dealing with more than one time zone Tom Tobin nobody "Django doesn't handle multiple time zones well. Datetimes are potentially ''stored'' with a time zone offset based on `settings.TIME_ZONE` (only for PostgreSQL), and ''retrieved'' as naive `datetime` objects. This is fine when working on a standard site publishing items within a single time zone, but quickly becomes pathological when working with more than one time zone, or when transitioning an existing site to a new time zone. I propose that Django's datetime handling be altered to ignore `settings.TIME_ZONE` on all database backends, and let the appropriate Fields handle time zone conversion. I've already written a `DateTimeZoneField` that appropriately handles multiple time zones and returns timezone-aware `datetime` objects; for it to work consistently, however, the PostgreSQL backends need to stop using `TIMESTAMP WITH TIME ZONE` and `SET TIME ZONE`. In summary: 1) The PostgreSQL backends should ignore time zones completely. 2) An appropriate `Field`, rather than a backend, should handle time zone support; such a field would require its backend storage to always be UTC, which can only happen cleanly if the backend ignores time zones. Discussion thread: http://groups.google.com/group/django-developers/browse_thread/thread/b8c885389374c040" defect new Core (Other) normal mike.scott@… korpios@… Accepted 0 0 0 0