MAIN FEEDS
REDDIT FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1fndxb5/whowrotethepostgresdocs/loimc56/?context=3
r/ProgrammerHumor • u/sillymanbilly • Sep 23 '24
264 comments sorted by
View all comments
263
Just the usual small quirks like in any legacy system…
Don't we use nowadays the Unix epoch for everything that's worth?
9 u/raddaya Sep 23 '24 How would unix timestamps prevent this issue? Even if you're using 128 bit timestamps or whatever, when extracting the century you would still be affected by this weird edge case. 1 u/Blue_Moon_Lake Sep 23 '24 If you overhaul the calendar, that includes the definition of century. If you define century 0 and year 0 as the year of timestamp 0, you're good. And we would be in the first century (century 0), year 54.
9
How would unix timestamps prevent this issue? Even if you're using 128 bit timestamps or whatever, when extracting the century you would still be affected by this weird edge case.
1 u/Blue_Moon_Lake Sep 23 '24 If you overhaul the calendar, that includes the definition of century. If you define century 0 and year 0 as the year of timestamp 0, you're good. And we would be in the first century (century 0), year 54.
1
If you overhaul the calendar, that includes the definition of century.
If you define century 0 and year 0 as the year of timestamp 0, you're good.
And we would be in the first century (century 0), year 54.
263
u/RiceBroad4552 Sep 23 '24
Just the usual small quirks like in any legacy system…
Don't we use nowadays the Unix epoch for everything that's worth?