On Mon, Aug 12, 2019 at 5:42 AM Simon Slavin <slav...@bigfraud.org> wrote:
> On 12 Aug 2019, at 1:27pm, Tim Streater <t...@clothears.org.uk> wrote: > > > 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. > > If the timezone is stored, then the time is all UTC and easily sortable. A sub-order of timeone within a sepcific time sequence ends up happening *shrug* But then, I'm assuming the time would just be ISO8601; since SQLite datetime functions take that as an input already. > I'm with Tim. Storing the time zone with the timestamp is a different > matter. It leads to problems with sorting and searching. We can discuss > it, but it doesn't belong in this thread. > _______________________________________________ > 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
