> The calendrical calculations always assume a Gregorian calendar, with no leap ... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

nottorp 8 months ago | parent | context | favorite | on: Show HN: High-precision date/time in SQLite

> The calendrical calculations always assume a Gregorian calendar, with no leap seconds.

That could drift a bit if you can represent a 580 million year interval (with millisecond precision), wouldn't it?

Someone 8 months ago [–]

A library that handles leap seconds can’t do much better, as it’s as good as impossible to predict leap seconds, certainly not that far ahead.

Luckily, leap seconds are on the way out (https://en.wikipedia.org/wiki/Leap_second#International_prop...)

Join us for AI Startup School this June 16-17 in San Francisco!
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact