The Django UUID Story
summary
Story shows concrete changes: contrib.postgres adds database-side UUIDv4 generation so a data migration can backfill 10,000+ rows with one SQL update instead of per-row Python defaults; Postgres later exposes UUIDv7 time-ordered IDs and Python 3.14 adds UUIDv7 support; Django exposes DB defaults across backends (merged around Django 5.0 and expanded in Django 6.1) so apps can choose DB-generated UUIDs or Python-generated UUIDs depending on backend and schema needs.
AI-written summary · about
chapters (23)
- 0:00Introduction and welcome
- 0:24Django UUID field introduction
- 1:35Speaker background and context
- 2:20Project challenges and inspiration
- 3:53First contribution to Django
- 6:31Benchmarking and improvements
- 7:40DjangoCon Europe 2017 sprints
- 9:10UUID field evolution in Django
- 10:20Historical context of UUID in Django
- 11:24DjangoCon Europe 2022 sprints
- 12:32Python 3.14 and UUID version 7
- 13:46Postgres 18 and UUID version 7
- 14:33Django on the Med 2025 insights
- 15:17New feature repository discussion
- 16:26UUID version 7 in SQLite
- 17:39Custom database functions in Postgres
- 18:50UUID extraction at database layer
- 19:34Django 6.1 UUID support
- 20:42Database support comparison
- 21:51Contributing to open source
- 22:57Call to DjangoCon US sprints
- 23:45DjangoCon Europe 2025 announcement
- 24:30Q&A and closing
