hishtory/client/lib/goldens/TestSortByConsistentTimezone-query

Hostname   CWD    Timestamp                 Runtime  Exit Code  Command       
localhost  /tmp/  Apr 16 2022 01:36:26 PDT  1s       2          third_entry   
localhost  /tmp/  Apr 16 2022 01:19:46 PDT  1s       2          second_entry  
localhost  /tmp/  Apr 16 2022 01:03:06 PDT  1s       2          first_entry
Store timestamps in DB in Unix time, and display them in the Local time for consistent TZs in displays, and to ensure ordering is correct This fixes a bug where entries could be out of order if they were recorded on machines in different TZs (e.g. if one machine had the TZ set to UTC). Admittedly, this commit isn't a perfect fix since it doesn't change all the existing hishtory entries to be stored in UTC, but this just means that the ordering bug will continue to exist for historical entries, but be fixed for new entries. And for our purposes, that is good enough. :) # Please enter the commit message for your changes. Lines starting 2023-09-09 21:28:01 +02:00			`Hostname CWD Timestamp Runtime Exit Code Command`
			`localhost /tmp/ Apr 16 2022 01:36:26 PDT 1s 2 third_entry`
			`localhost /tmp/ Apr 16 2022 01:19:46 PDT 1s 2 second_entry`
			`localhost /tmp/ Apr 16 2022 01:03:06 PDT 1s 2 first_entry`