On 12 Aug 2019, at 12:41, Thomas Kurz <sqlite.2...@t-net.ruhr> wrote:
> The problem is not only about storing an arbitrary integer or float number. A > date is much more, it has timezone information with it, and I would like to > see a DATE column handle this in a proper and well-defined way, just as a > calendar (CalDAV) does handle it, so it would allow me to convert between e.g. > EST and CEST or calculating time differences (e.g. working time in a company). > I know many of this is somehow possible now as well, but as far as I know, not > really compliant with other RDMSs. I don't expect to do that with SQL. My "seconds since the epoch" is based on converting any particular time to GMT and storing that. That number is then converted to a date/time with TZ info for display. -- Cheers -- Tim _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
