On 2011-06-02, at 12:34 AM, Stephen Burrows wrote: > Django actually already adds support for some capabilities to certain > database backends, if I'm not mistaken - such as cascades through GFKs > on delete. > > In terms of time zones, could django "assume"/ensure that the datetime > stored in the backend is UTC, then handle the conversion to the local > timezone itself?
Isn't this a viable solution? It's the universal, cross-timezone-friendly datetime objects that we care about, not the timezones they were in, right? - If the DB supports timezone-aware datetime fields, just pass the datetime object through as is. - If the DB doesn't support timezone-aware datetime fields, convert to UTC and store the datetime as UTC - If the datetime has tz info, convert the time to UTC using that - If the datetime doesn't have tz info, convert using the default timezone specified in the settings When retrieving the data from a non-timezone-aware db, convert them from UTC to the project's timezone. Sam -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
