I should also mention that the concept of localized time is subject to the whim of politicians and the crap implementations of localtime conversions in much software. Usually software knows when "now" is in UT1 (even if expressed with the currently known offset from UT1), it is still a UT1 instant time.
This is especially true when such systems use time synchronization software such as NTP or PTP or the many like systems, no matter what the synchronization base (whether TAU, UTC, UT1, or other source). --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of Jens Alfke >Sent: Friday, 25 August, 2017 10:46 >To: SQLite mailing list >Subject: Re: [sqlite] Date time functions not working > > > >> On Aug 24, 2017, at 6:28 PM, Keith Medcalf <kmedc...@dessus.com> >wrote: >> >> Timezone is something that is applied and removed at the User >Interface level and should never exist below the presentation level. > >There are cases where the timezone needs to be preserved in the data >model because it can be important to know the local time >corresponding to the event. A common example is email: the Date >header includes a timezone, so that the recipient can tell what the >local time was. For instance, it can be significant to know whether >it was 2PM or 2AM local time when a co-worker sent you a grumpy email >about a bug. (The same goes for other communications like blog posts >and chat messages.) > >—Jens >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
