> keep in mind that Integers support One percision, and there’s a trade off between resolution and the bounds of your epoch, Floating point values support all p

> keep in mind that Integers support One percision, and there’s a trade off between resolution and the bounds of your epoch, Floating point values support all percisions, there is no such trade off. Yeah, except with integers you get guaranteed precision across all of your data range while with floating point, it is ridiculously easy to accidentally lose precision without noticing it when e.g. shifting time deltas from the past into the future. Not to mention that using floating-point number of seconds since epoch means that the times around the epoch are always given better precision than the timestamp around the current time which is really not what you want, and the situation only worsens with time.