On Thu, Sep 3, 2009 at 11:36 PM, Margie Roginski<margierogin...@yahoo.com> wrote: > > I've created a django app and I soon am going to have users that are > in multiple timezones. My app is a task management system and it is > important for users to see dates and times with respect to their own > time zone. IE, if here in California I create a task at 3PM on Sept > 3, I want someone in India to see it as being created at 1AM on Sept > 4. Optimally, if that India employee travels to the US and looks at > the task creation date, they should see 3PM on Sept 3. Is there a > "best" way to handle this? Things that come to mind are: > > 1. Create a deployment for each of my time zones where TIME_ZONE and > DATE_FORMAT are set appropriately for the time zone associated with > the deployment. This seems painful ... > > 2. Have a single deployment and whenever I display dates, use some > sort of tag that can figure out how to display the date correctly > based on the user's time zone > > 3. I see there is a reusable app called django-timezones. There is > not much doc with it, but I'm guessing this is targeted at what I am > trying to do. > > Can anyone give any recommendations? I'm happy to dive in and read > source (ie, for django-timezones app), but I just want to make sure > I'm heading in the right direction. > > Thanks,
have you tried to use postgres timestamp with time zone field? It has ability to make such a conversion on the fly and every date can be stored with timezone --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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 -~----------~----~----~----~------~----~------~--~---
