Oops - typo in my post above. Unix is of course secs since 1970. and Tim yes I too always use numerical dates - each to their own though - my post wasn't trying to say what is best, just what I see.
Paul www.sandersonforensics.com skype: r3scue193 twitter: @sandersonforens Tel +44 (0)1326 572786 http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit -Forensic Toolkit for SQLite email from a work address for a fully functional demo licence On 8 March 2017 at 22:57, Tim Streater <t...@clothears.org.uk> wrote: > On 08 Mar 2017 at 20:40, Paul Sanderson <sandersonforens...@gmail.com> > wrote: > > > The vast majority of dates I see in SQLite databases are unix epoch > integer > > times (seconds since 1/1/1980) with unix milli seconds a close second. > > Efficient to store, sort and do date arithmetic on but need to be > converted > > to display. > > This is also what I do; seconds since the epoch. I can't imagine string > dates or times as strings. You're also going to need to give the user the > option to select their date/time format, too, so converting to display > should be done at display time, not before. > > -- > 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
