On Fri, Apr 9, 2010 at 2:48 PM, Ramiro Morales <cra...@gmail.com> wrote: > On Fri, Apr 9, 2010 at 3:20 PM, Tom X. Tobin <tomxto...@tomxtobin.com> wrote: >> >> This reminds me that we need to open-source our time zone code. We >> track entertainment events across several time zones, and Django's >> standard time handling can't cleanly deal with that. Database >> backends that store time zones as a UTC offset (e.g., PostgreSQL) >> actually cause *more* trouble because UTC offsets are not the same >> thing as time zones; it's always safest to store times as UTC and > > We've solved this particular hurdle in r12602 when fixing bug #1480 > but of course more work is needed for a full solution.
I've banged my head against time zone issues for long enough to have a pretty good understanding of just how tricky time zones are. We shouldn't be handing PostgreSQL anything but UTC times in a timestamp column, since Postgres operates in terms of UTC offsets rather than actual time zones. Storing a time with a UTC offset is worse than useless, since it doesn't tell you *anything* about the actual time zone in question; time zones are political (rather than rational) beasts. > We added this featur as an idea for this year GSoC program > > http://code.djangoproject.com/wiki/SummerOfCode2010#Multipletimezonesupportfordatetimerepresentation > > So far, no student expressed interest in it, maybe we can > propose it as a feature for 1.3 when the time comes. We've got working code for single-site multiple-time-zone support that's been in production use for a good year now, and again, I'm happy to push it up onto GitHub as soon as I get a chance to extract it from our repository. It doesn't require modifying Django, either; you just use the new model fields and you're good. Hopefully someone else will find it useful once it gets polished and has docs. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
