BEGIN:VCALENDAR PRODID;X-RICAL-TZSOURCE=TZINFO:-//Calagator//EN CALSCALE:GREGORIAN X-WR-CALNAME:Calagator METHOD:PUBLISH VERSION:2.0 BEGIN:VTIMEZONE TZID;X-RICAL-TZSOURCE=TZINFO:America/Los_Angeles BEGIN:DAYLIGHT DTSTART:20260308T020000 RDATE:20260308T020000 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT CREATED;VALUE=DATE-TIME:20260813T175941Z DTEND;TZID=America/Los_Angeles;VALUE=DATE-TIME:20260908T203000 DTSTART;TZID=America/Los_Angeles;VALUE=DATE-TIME:20260908T183000 DTSTAMP;VALUE=DATE-TIME:20260813T175941Z LAST-MODIFIED;VALUE=DATE-TIME:20260813T175941Z UID:http://calagator.org/events/1250482662 DESCRIPTION:Please note different time and location this month at [UpStar t Collective](https://www.upstartcollective.org/) at the U.S. Bancorp To wer (a.k.a. Big Pink). Please RSVP on MeetUp. Tuesday September 8\, 20 26 from 6:30pm to 8:30pm. \;\n \;\nCoinciding with [devopsdays Por tland\, OR](https://devopsdays.org/events/2026-portland-or/welcome/)\, S ept 8-10\, 2026. \;\n \;\nIn v18\, Postgres got temporal primary k eys\, unique constraints\, and foreign keys (with `NO ACTION`). Hopefull y in v19 we'll have `UPDATE/DELETE FOR PORTION OF`. So it's a good time to start thinking about migrating your schema to a temporal structure. S ome advantages include: \;\n \;\n- Easier queries and joins to rec onstruct historical data. \;\n- A better way to do soft-deletes (pres erving referential integrity). \;\n- No bugs from foreign key referen ces to since-updated data. \;\n- A less ad hoc way of representing hi storical data. \;\n \;\nThis talk will explore how to migrate your schema to include application-time `daterange` and `tstzrange` columns. I'll use an existing schema for a time-tracking and invoicing applicati on (used by me for over 12 years)\, showing the pain points of the old s tructure\, not sparing my pride at some bad decisions\, and give an appr oach to bring it all into a nicer temporal structure. \;\n \;\nWe will also talk about some remaining pain points in using temporal tables \, and suggestions to mitigate them. \;\nIf you are contemplating a m ove to temporal tables\, this talk will give you an overview of the land scape. \;\n \;\nPresented by Paul Jungwirth: \;\n \;\nPaul i s a freelance software developer in Portland\, Oregon. \;\nHe has bui lt applications with Postgres since 2010 and is the author of several ex tensions. \;\nHis Postgres contributions include work on GiST indexes \, multiranges\, and SQL:2011 application-time features.\n\nTags: postgr es\, postgresql\n\nImported from: http://calagator.org/events/1250482662 URL:https://www.meetup.com/pdxpug/events/316102878/ SUMMARY:PDXPUG MeetUp: Migrating to a Temporal Schema LOCATION:Upstart Collective: 111 SW 5th Ave\, Portland Oregon 97204 US SEQUENCE:1 END:VEVENT END:VCALENDAR