On Wed, 2009-11-25 at 10:52 -0800, Rob Hudson wrote: > I like the solution proposed on ticket 10587: > http://code.djangoproject.com/ticket/10587 > > Basically, it proposes that timezones are handled analogous to how > Unicode is handled -- that is, everything within Django boundaries is > treated as UTC, with timezone conversions happening on input and > output, but never within Django and always stored as UTC in the > database.
I'm +1 on this idealistic solution. But what about the backwards compatibility for already persisted dates in a timezone different from UTC?
signature.asc
Description: This is a digitally signed message part
