mikewhit wrote: > > Using UTC in the DB stops you going mad when something happens > on the DST changeover (localtime hours vanish, or happen twice), > or you have systems running in or across different countries. > > It also means you can subtract two times and always get the right answer > for elapsed time ! >
Yes, as pointed out in my original post, I've heard the arguments for using UTC time. Folks are just going to need to trust me to make the decision as to how appropriate this approach is for my particular project. BTW, MS SQL Server doesn't do anything like this as far as I know. Given some of the comments here, one might wonder how those poor MS SQL Server folks are able to get anything working at all. ;-) -- View this message in context: http://www.nabble.com/CURRENT_DATE-Behavior-tp20075044p20099042.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
