Always store everything as utc. That ensures that the data you are working with is clearly defined and consistent. If you want the times to be displayed (or input) according to the user's timezone, that is a detail of the presentation and UI, not of the underlying data.
On Thu, Apr 3, 2008 at 1:05 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > So far I've been storing time stamps in my mysql database just using > datetime.datetime.now()....but I'm wondering if that's the right thing > to be doing? > Am I perhaps better off storing everything in utc time? How do other > people deal with this? I noticed that postgresql seems to have > datatypes for storing date-times including the timezone but mysql > lacks this. So perhaps the best strategies are different for > different databases? > > What method are people using to discover the timezones of their > clients? > > Thanks! > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
