Re:64-bit unix timestamp is not supported in MySQL functions...
by oarabbus_ on Tuesday December 10, 2019 @08:00PM
(#21758529)
Reason 34,583,498 to use Postgres instead of MySQL.
[ Parent
| on HN ]
Re:64-bit unix timestamp is not supported in MySQL functions...
by q3k on Tuesday December 10, 2019 @08:07PM
(#21758568)
Also to not use the TIMESTMAP type in general, which is full of similar by-default footguns (off the top of my head: default 1-second precision, connection-local timezone autoconversion). At least for non-historic events.
Use uint64 as nanoseconds from epoch. Explicitly convert to/from UTC in your application code. Smear your leap seconds. This will last you until 2554, by which time I hope computers as we know are dead. Bonus: these make for decent strong-read-ordered internal UUIDs, given good retry logic.
Re:64-bit unix timestamp is not supported in MySQL functions...
by jpeg_hero on Tuesday December 10, 2019 @10:32PM
(#21759312)
I am looking at just this design pattern now (pseudo uuid) can you elaborate on “given good retry logic”?