@Unionhawk Oh man, I had that happen a couple years ago as I was leaving for a trip

@Unionhawk I should probably make a dentist appointment sooner rather than later. One of my wisdom teeth got chipped months ago, but I'm afraid of making a dentist appointment

Man, I am an expert at putting off things I don't want to do

Had some bad experiences with my previous dentist because I think the local anesthetic that the dentist injects into your gums before drilling doesn't really work with me. I still feel the dentist drill

Skyrim, for all the times it's memed about being put on every system, is finally on GOG

Wtf

So I was writing a sync process to pull data from one database into another

In the table in the old database there was a StartDate field that was an integer, so obviously it was a unix timestamp, right?

Yeah, no

It was a date stored as an integer like "20220929"

Man I loved the year 2.01x10^7

@SaintWacko at least it's YYYYMMDD...

Ah yes, august 23 1970

That reminds me of an api that I was using that returned dates in seconds rather than milliseconds from 1970, which was fun for a bit

@Ronan seconds is actually the standard, but most people need the precision of milliseconds

Oh I didn't know that, I just know javascript uses milliseconds, so I was confused when all the dates were wrong

@Unionhawk Yep, all the dates in the new app table were in 1970 -.-

@MBraedley I think it's that seconds is a unix timestamp and milliseconds is a file timestamp? Something like that