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. -- View this message in context: http://www.nabble.com/CURRENT_DATE-Behavior-tp20075044p20104213.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
