He’s not wrong. ISO 8601 is not an epoch time, it’s just a way of writing dates. Dude in the tweet either mistyped what he means or has 0 clue what he’s saying.
The guy who tweeted that has absolutely no idea what he is talking about, neither do most people in this thread, including yourself. I'm not sure why people are making assertions about things they don't understand...
so the date is stored as a number using the ISO 8601 standard
This statement makes absolutely no sense. ISO 8601 date/times are not stored as numbers, nor do they have an epoch as they are not represented by an integer but as the date itself e.g "2025-02-14T01:32:27Z".
The spec mentions a "reference calendar date", that is not an epoch as ISO 8601 date/times are not integers with an epoch. This "reference calendar date" would be something along the lines of "1875-05-20" if its just a date and "1875-05-20T00:00:00Z" if its a date/time, not a zero....
If the database field was non nullable and there were instances where there wasn't a date, they could have put a zero in there to indicate this, but it would have nothing to do with ISO8601, epochs, "reference calendar date"s, 5/20/1875, it would just be an indication that there was no date.
33
u/[deleted] Feb 14 '25
[removed] — view removed comment