On Mon, Aug 12, 2019 at 6:54 AM Tim Streater <t...@clothears.org.uk> wrote:
> On 12 Aug 2019, at 14:30, J Decker <d3c...@gmail.com> wrote: > > > 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* > > Why are you storing the timezone? You display the TZ of the user who is, > later, viewing the data. And that user could be anywhere. Because the actual time on the clock on the wall matters. I want to know cashiers that are making transactions outside of 9am-5pm (for instance). But depending on where they are that time is different. I also want to know the time continuously according to the linear time that they happened in. > > But then, I'm assuming the time would just be ISO8601; since SQLite > > datetime functions take that as an input already. > > I'm a user; I don't want my times displayed as ISO8601. That's why we have > date/time control panels so the user gets to choose how those are displayed. > > Then strftime it. I don't want to see PK/FK identifiers either. > > -- > Cheers -- Tim > _______________________________________________ > 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
