pphysch on British Columbia, Time Zones, and Postgres

Comment on British Columbia, Time Zones, and Postgres parent

These aren't global timezone changes, these are changes to individual or small batches of timezones. If you are not scheduling future events in these timezones, they do not affect you. You are welcome to overengineer systems to possibly prevent potential future timezone-shift-caused data corruption. Unless I ran a globally distributed appointment/event database, I would personally avoid doing that.

dqv 2mo

"overengineering"

    UPDATE appointments
    SET starts_at_utc = local_time AT TIME ZONE timezone_name
    WHERE timezone_name = 'America/Vancouver'
      AND starts_at_utc > now();

pphysch 2mo

You elided the part where you are adding an extra column to your database just for this rare corner case.

Comments