BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.evolutio.pt//djangocon-europe-2026//FZCKT9
BEGIN:VTIMEZONE
TZID:EET
BEGIN:STANDARD
DTSTART:20001029T050000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EET
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-djangocon-europe-2026-XBBRYC@pretalx.evolutio.pt
DTSTART;TZID=EET:20260417T124000
DTEND;TZID=EET:20260417T131000
DESCRIPTION:We're all familiar with Django's `atomic` context for managing 
 database transactions\, but Django existed for several versions before it 
 existed. How were transactions managed before 2013? How are transactions m
 anaged now? And how might they be managed in the future?
DTSTAMP:20260502T004643Z
LOCATION:AMPHITHEATRE
SUMMARY:Where did it all `BEGIN\;`? - Sam Searles-Bryant\, Charlie Denton
URL:https://pretalx.evolutio.pt/djangocon-europe-2026/talk/XBBRYC/
END:VEVENT
END:VCALENDAR
