jonwood wrote: > > cmartin-2 wrote: > >>I suspect it is quite common, e.g., web apps built on SQLServer backends >>are quite likely to use UTC. At any rate, it is definitely a design >>decision, if one expects that local times will always work in all >>scenarios, but all means use local times. If design criteria change >>unexpectedly in the future to the point where local times become >>problematic, for reasons already mentioned, it will need a redesign. By >>using UTC from the outset, it will be robust to all possible >>datetime-related needs in the future. >> > > > Yeah, I appreciate the discussion of UTC. Although I don't fully understand > how to convert UTC to local time on a Website, I do some Web development and > so I can imagine scenarios where they may be appropriate.
Use the timezone environment variable or similar. You always stay out of trouble and fit in with best practice if you use UTC. If you use local time you also need to store the TZ. See ISO8601 for the format (e.g. 2008-10-22 14:39Z where Zulu time is UTC). _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
