On Wed, Jun 2, 2021 at 3:23 PM Joris Peeters <joris.mg.peet...@gmail.com> wrote:
> You could store epoch offsets, but interpret them in the local timezone. > E.g. (0, "America/New_York") could mean 1970-01-01 00:00:00 in the New York > timezone. > At least one nasty problem with that is ambiguous times, i.e. when the > clock turns back on going from DST to ST, as well as invalid times (when > the clock moves forwards, meaning some epoch offsets never occur). > Another problem is calendars change (see Adam's points) so the offset would not be constant.
